Loading...
Loading...
Found 6,716 Skills
Legacy-project style inheritance skill. Use when the user types /inherit-legacy-style, or when onboarding an AI coding agent onto a hand-written legacy project and you need to prevent "style drift" (the model imposing its pretrained mainstream idioms onto the project). Language- and framework-agnostic — it aligns meta-architecture only, not syntax. Once run, it becomes a behavioral constraint on all subsequent coding tasks. Do NOT use for pure research or one-off questions unrelated to code-style alignment.
Continuously question users about their plan or design. Suitable for scenarios where users want to stress-test their plan before building, or when using any "grill" trigger phrases.
Realm integration. Manage data, records, and automate workflows. Use when the user wants to interact with Realm data.
Structured code review using tiered persona agents, confidence-gated findings, and a merge/dedup pipeline. Use when reviewing code changes before creating a PR.
Audit, prune, and improve agent guidance markdown files in repositories. Use when the user asks to check, audit, update, improve, or fix AGENTS.md, CLAUDE.md, or related guidance files. Adds missing commands and gotchas, removes stale entries, deduplicates, and keeps the file small and relevant. Scan for guidance files, evaluate quality against templates, output a quality report, then make targeted updates.
Read a local source file or synthesize conversation context, then integrate admitted content directly into topic, entity, concept, and analysis pages in existing memory (the wiki substrate). Use this when the user wants to add a source to the wiki, add a document, ingest a local note, transcript, article, report, or PDF, or explicitly preserve the current conversation as a topic note. For session-learning routing across wiki, guidance, checkpoint, task annotation, or discard, use /loam::learning-from-session. Must not ingest a goal wholesale; admit only independently reusable findings.
Design evidence-led before-and-after short-form ads from product facts, approved proof, reference analysis, or rough concepts. Use for before/after ads, transformation ads, problem-solution-result UGC, skincare/body/wellness routines, visual comparison scripts, or approved before-after scripts that should proceed to image-batch-runner or video-batch-runner.
Comprehensive review of local uncommitted changes using specialized agents with code improvement suggestions
Construir a documentação técnica em docs/ e o inventário npm/Composer em .specsfy/PACKAGES.md. Use ao documentar sistemas ou após implementações.
Use when symfony doctrine transactions
Reconcile the project's FPF state with recent repository changes
Create Requirements Document - generates a structured requirements document, asking clarifying questions about ambiguities before proceeding