Loading...
Loading...
Found 149 Skills
Constructive critique through 5 HackerNews commenter personas with evidence-based claim validation. Use when user wants devil's advocacy, stress testing, or critical review of ideas, docs, architecture, or code. Use for "roast", "critique this", "poke holes", "devil's advocate", "stress test", or "what's wrong with". Do NOT use for code review (use systematic-code-review), implementation changes, or performance profiling without a specific critique request.
Mobile development patterns for React Native and Flutter including navigation, state management, and responsive design
Full-pipeline iOS App Store opportunity research. Discovers underserved niches, analyzes competitor gaps, estimates revenue, produces scored top-3 opportunity reports, and writes MVP PRDs — all through browser and web research. Use when the user wants to find profitable iOS app ideas, research App Store charts, analyze competitor apps (ratings, reviews, revenue, gaps), generate opportunity reports, or write MVP PRDs. Triggers on "find app opportunities", "app store research", "what app should I build", "research this app category", "find a gap in the app store", "ios app ideas".
Structured specification with explicit scope boundaries: user stories, acceptance criteria, out-of-scope definition, risks, and estimation. Positions before feature-design in the feature lifecycle pipeline. Use when: "write spec", "user stories", "define requirements", "scope this", "what should this do", "acceptance criteria", "define scope"
Generate headless Claude Code cron jobs from a task description and schedule. Creates a wrapper script with safety mechanisms (lockfile, budget cap, dry-run default, logging) and installs crontab entries via deterministic Python script. Use when user says "schedule", "run every", "cron job", "run twice daily", "run hourly", "run daily", "run weekly", or "schedule task".
Pre-publication validation for Hugo posts: front matter, SEO, links, images, draft status, and taxonomy. Use when user wants to check a post before publishing, validate blog content, or run pre-publish checks. Use for "pre-publish", "check post", "ready to publish", "validate post", or "publication check". Do NOT use for content writing, editing prose, or generating new posts.
4-phase code review methodology: UNDERSTAND changes, VERIFY claims against code, ASSESS security/performance/architecture risks, DOCUMENT findings with severity classification. Use when reviewing pull requests, auditing code before release, evaluating external contributions, or pre-merge verification. Use for "review PR", "code review", "audit code", "check this PR", or "review my changes". Do NOT use for writing new code or implementing features.
Spawn 10 independent parallel agents to analyze source material from distinct perspectives, synthesize findings, and apply improvements to a target agent or skill. Use when source material is complex and multi-angle extraction justifies 3-5x token cost over inline analysis. Use for "parallel analysis", "multi-perspective", or "deep extraction". Do NOT use for routine improvements, simple source material, or when token budget is limited.
Merge validated feature to main via PR, tag release, cleanup worktree. Use after /feature-validate passes. Use for "release feature", "merge feature", "ship it", or "/feature-release". Do NOT use without passing validation or for hotfixes that skip the pipeline.
Produce first drafts that match a writer's authentic voice using their Voice DNA Document. Consumes DNA documents from writing-dna-discovery skill. Generates 2 meaningfully different drafts with headlines, confidence assessment, decision notes, and DNA refinement suggestions. Collaborative partner that evaluates, pushes back, and advocates for quality. Handles blog posts, essays, newsletters, and more.
Critique-and-rewrite enforcement loop for voice fidelity. Validates generated content against negative prompt checklists and forces revision until it passes. Use when content has been generated in a target voice, voice output feels off, long-form content risks voice drift, or before final delivery of voice content. Use for "validate voice", "check voice", "voice feels wrong", "voice drift", or "rewrite for voice". Do NOT use for initial voice generation, voice profile creation, or content that has no voice target.
Collaborative coding with enforced micro-steps: announce, show diff, wait for confirmation, apply, verify. User controls pace with commands. Works with any domain agent as the executor. Use when: "pair program", "pair with me", "let's code together", "step by step coding", "walk me through implementing", "code with me"