silkyland
- 17 skills
- 0 followers
- 13 hours ago last updated
- ▌ Ask My Repo · silkyland bundleThree-mode repo knowledge skill for ANY codebase: INGEST builds cited knowledge files (AGENTS.md + docs/ARCHITECTURE.md) so any AI agent can understand the codebase without re-searching it; UPDATE re-verifies and merges changes into existing knowledge without overwriting; QUERY answers natural-language questions about the repo by reading the knowledge first, then drilling into code only when needed, with file:line citations. Use whenever the user asks to ingest/onboard/understand a repo, update or refresh repo knowledge/docs, or asks any question about a codebase's architecture, modules, conventions, where things live, or how something works — even if they don't say "ask-my-repo". Works on any repo, no hardcoded paths. Trigger phrases: "ask my repo", "query the codebase", "ingest this repo", "update repo knowledge", "how does X work in this repo", "where is X", "explain the architecture", /ask-my-repo.
- ▌ Clean Slate · silkyland bundleRe-initializes a project's agent knowledge from scratch when the existing knowledge files (CLAUDE.md, AGENTS.md, cursor rules, architecture docs, roadmaps, old plans) have rotted, contradict the code, or accumulated too much noise to patch. Salvages still-true facts by verifying them against the code, asks the user about backup before deleting anything, re-reads the actual codebase fresh, interviews the user on the intended direction, and rebuilds strong AGENTS.md, docs/ARCHITECTURE.md, and ROADMAP.md. Use when the user asks to reset, re-initialize, or rebuild project knowledge or architecture docs, says the docs are stale or wrong, or mentions clean-slate or /clean-slate.
- ▌ Create My Team · silkyland bundleGeneral-purpose multi-agent teamwork: for any sizable task, probes what subagent-spawning capability the current platform actually exposes (Claude Code agents/workflows, Codex multi-agent tools, OpenCode subagents — or none, with an honest sequential fallback), designs a team topology sized to the task (scout swarm, pipeline, panel-and-judge, manager-worker), sends every member a standardized mission brief, researches BEFORE executing, presents the synthesized plan at a user gate, then spawns the execution team and cross-checks every deliverable at an integration gate before merging. Use when the user wants to spawn agents or subagents, parallelize research or work across a team, says "use a team/multi-agent" for a task, or mentions create-my-team or /create-my-team.
- ▌ Ground My Shopware · silkyland bundleBuilds and repairs Shopware 6 Administration and Storefront UI by reading the INSTALLED vendor source first — `mt-card`'s real slot list, `sw-data-grid`'s preview slot, `sw-modal`'s variants, the Meteor token files, the snippet catalogues — and reusing the component core already ships instead of hand-rolling markup. Built for Shopware's silent failure class, where nothing throws: content addressed to a slot the component does not declare is dropped without a warning, a `variant="small"` media uploader renders no preview at all, a BEM class with no stylesheet leaves a section looking cramped, a scoped `.mt-card[data-v-…]` rule beats your single-class override and computes to `0px`, a required `description` prop passed as a bare attribute prints an empty block, a `<h3>` inside a `{# … #}` comment renders fine in the browser and crashes every template spec. Use this skill whenever the task touches a Shopware admin module, page, card, data grid, modal, media or colour picker, admin SCSS or snippets, a storefront
- ▌ Ground My UI · silkyland bundleDiagnoses and rebuilds UI that looks broken, ugly, or off-system by verifying every contract the code touches against the INSTALLED source on disk — component props, slot names, enum values, design tokens, icon names, i18n keys, and which element actually owns layout — before any redesign is attempted. Built for the failure class that raises no error: an invalid variant renders unstyled, a misspelled slot renders nothing, an undefined custom property voids the whole declaration, a missing translation key prints itself. Stack-agnostic (React, Vue, Svelte, Angular, Twig/PHP, Rails, SwiftUI, Compose, Flutter, .NET) and works inside any design system, then locks the verified contracts into tests. Use when a screen looks wrong, unstyled, misaligned, or inconsistent with its design system, when components render blank or ignore their props, when raw translation keys or unformatted values appear in the UI, when asked to redesign or restyle a view, or when the user mentions ground-my-ui or /ground-my-ui.
- ▌ Hospitable API · silkyland bundleInstructions for integrating with the Hospitable.com Public API (v2). Use this skill when the user asks to work with Hospitable properties, reservations, calendars, guests, messaging, reviews, payouts, transactions, inquiries, enrichable shortcodes, or webhooks. Trigger phrases: "connect to Hospitable", "fetch reservations", "block calendar dates", "send message to guest", "get reviews", "list payouts", "get transactions", "set wifi password shortcode".
- ▌ Jury My Repo · silkyland bundleMulti-agent adversarial audit: detects which AI coding agent CLIs are installed (Claude Code, Codex, Gemini CLI, OpenCode, Kimi, Cursor, Qwen, Aider, Goose, Crush, Droid, Copilot), runs the willing ones in parallel headless mode against the same audit brief in isolated read-only worktrees, collects each agent's bug/security/architecture findings separately, then cross-examines every claim against the actual code — CONFIRMED, REFUTED, or DUPLICATE — producing a per-agent scoreboard (precision, unique catches, hallucination rate) and one distilled, verified defect report. Use when the user wants a multi-agent audit or review, a second opinion from other AI agents, to compare coding agents on their codebase, or mentions jury-my-repo or /jury-my-repo.
- ▌ Know My Repo · silkyland bundleOnboards an agent onto an unfamiliar repository from zero knowledge: deep parallel read of the codebase, extraction of the repo's actual conventions (each proven by at least two examples), verified build/test/run commands, an end-to-end exemplar trace of how a feature is really added, then generates the initial knowledge set — AGENTS.md and docs/ARCHITECTURE.md — with every fact cited. Nothing is deleted. Use on repositories with no (or trivial) agent knowledge files, when the user asks to onboard, initialize, understand, or learn a repo, generate a CLAUDE.md/AGENTS.md from scratch, or mentions know-my-repo or /know-my-repo.
- ▌ Love Me Love My Docs · silkyland bundleAuto-generates a beautiful user manual with REAL screenshots captured by executable scripts: censuses the app's user flows from routes and navigation, builds a Playwright (Python) capture harness for web (the primary focus; mobile via Maestro is an optional path), seeds safe demo data so no real user data appears in images, writes the manual chapter-per-flow with a numbered step per screenshot, and renders it beautifully (MkDocs Material site, Markdown, or PDF). The capture scripts are committed, so the manual regenerates when the UI changes instead of rotting. Use when the user asks to generate a user manual, user guide, documentation with screenshots, onboarding docs, or mentions love-me-love-my-docs or /love-me-love-my-docs.
- ▌ Reproduce My Bug · silkyland bundleTurns a vague bug report into a minimal, runnable reproduction BEFORE any fix is attempted: sweeps evidence (logs, stack traces, git history around first-seen, DB state), ranks hypotheses by evidence, builds the smallest failing automated test (or repro script) that demonstrates the bug on demand, minimizes it until every remaining step is load-bearing, handles intermittent/flaky bugs by forcing determinism and documenting the reproduction rate, and delivers a repro dossier that hands the fixer a ready-made regression test. Never fixes — reproduces. Use when the user reports a bug, says something breaks sometimes or only in production, asks to investigate, debug, or find the root cause of an issue, or mentions reproduce-my-bug or /reproduce-my-bug.
- ▌ Seed Ah · silkyland bundleSeeds a database with data that looks like a real, lived-in production database: reads the real DB structure (migrations, ORM models, live introspection), builds a dependency-ordered seeding plan using the framework's own seeder mechanism, generates locale-correct identities, timestamps spread like history, power-law distributions and deliberate edge cases, and fills image fields with real licensed photos pulled from photo libraries (Unsplash, Pexels, Openverse, Wikimedia) instead of hand-drawn placeholders. Nothing in the seeded rows says "demo", "test", "sample" or "lorem" — provenance is kept in an invisible ledger so every row stays wipeable. Hard production gate: verifies the target database before writing a single row. Login accounts and credentials are produced ONLY when the user explicitly asks for them. Use when the user asks to seed demo/test/sample data, create fixtures, populate a dev database, or mentions seed-ah or /seed-ah.
- ▌ Transform My Repo · silkyland bundleFeasibility analysis and migration strategy for architecture transformations: language ports (PHP to Python, Rust to Go), framework migrations (Vue or React SPA to Next.js), major version upgrades, monolith to microservices and back, database migrations, cloud/container/ serverless re-hosting, sync to event-driven, REST to GraphQL/gRPC, UI platform shifts, standalone to SaaS, and vanilla to framework. Produces an evidence-based GO/PARTIAL/NO-GO verdict with a worth-it test against the do-nothing baseline (dependency census verified in the target ecosystem, semantic gap analysis, per-module difficulty heatmap), then a migration roadmap with behavioral parity gates and rollback points. Allowed to recommend NOT migrating. Use when the user asks to migrate, port, rewrite, re-platform, upgrade a major version, split or merge services, switch databases or API paradigms, asks whether a migration is worth it, or mentions transform-my-repo or /transform-my-repo.
- ▌ Twin My Site · silkyland bundlePlans a native mobile companion app for an existing website — a twin, not a wrapper: same brand DNA, data, and features; native body. Censuses the web product's features and classifies each for the app, audits API readiness and designs the mobile API contract (token auth, pagination, media, push pipeline), extracts the web's design language into mobile design tokens translated to native idioms, commits to an app stack, prepares the store listing (app name, description, category, privacy policy and account-deletion links — recommending generators when missing — and a scaffolded store/ publish kit), and writes a phased blueprint starting with a walking skeleton. Use when the user has a website and wants a mobile app version or companion app, needs an API designed for an app, wants the app to match the web's design and tone, asks to prepare an App Store or Play Store listing, or mentions twin-my-site or /twin-my-site.
- ▌ Deep Plan · silkyland bundleResearch-first, evidence-first implementation planning in seven gated phases: frame the task, inventory the real codebase, verify ground truth from vendor source or official docs, adversarially audit existing code, analyze gaps, commit to design decisions, and write a phased plan document with timeline, risks, and verification. Enforces "no claim without evidence, no design before research". Use when the user asks to plan, design, architect, audit, or review before implementing a feature, refactor, migration, or system, or mentions deep-plan, /deep-plan, or Plan mode.
- ▌ Deep Plan Ingest · silkyland bundleDistills a completed deep-plan document (e.g. docs/PLAN.md) into durable project knowledge files: AGENTS.md (agent operating rules and verified ground truth), docs/ARCHITECTURE.md (component map, data flow, framework mechanisms with citations), and ROADMAP.md (phased roadmap with live status). Carries only VERIFIED evidence forward, re-checks stale claims, and merges into existing files instead of overwriting. Use after a deep-plan finishes, when the user mentions deep-plan-ingest or ingest the plan, or asks to generate/update AGENTS.md, ARCHITECTURE.md, or ROADMAP.md from a plan.
- ▌ API Football V3 · silkyland bundleComprehensive development guide for integrating the API-Football v3 API (api-sports.io). Covers authentication (header-based API key), rate limiting, all 38 endpoints grouped by category, TypeScript types, caching, error handling, and security. Triggers on any task involving football livescores, fixtures, standings, odds, transfers, player stats, or team data from API-Football.
- ▌ Thscore Football API · silkyland bundleComprehensive development guide for integrating the THScore Football API. Covers authentication, regional server selection, all football endpoints (Live Data, Stats, Odds, Live Animation, Historical DB), TypeScript types, rate limiting, caching, error handling, and iFrame/WebView embedding. Triggers on any task involving football livescores, schedules, standings, odds, events, lineups, team/player profiles, or live animation embeds.