saif-shines

Verify agent-context quality with the `dora` CLI. Whenever you author or edit a skill (SKILL.md), plugin, rule, or agent config, run dora to check it before reporting the work done. Also use when the user asks to check, diagnose, fix, or clean up agent context across Claude, Cursor, Codex, Copilot, or Grok. Not for ordinary source-code edits.

Use when testing scenario coverage in review tier 3.

Nested skill under packages/x/skills, used to test recursive discovery.

First skill in the multi-skill fixture repo, used to test fan-out validation.

Second skill in the multi-skill fixture repo, used to test fan-out validation.

Extracts examples for testing the agentskills.io spec validator. Use when validating a well-formed skill against the open spec.

Valid description, but the name field does not match the parent directory name.

Body deliberately exceeds the Level 2 line/token budget to exercise the progressive-disclosure warning.

Author, review, and package freeCodeCamp publication tutorials against the official Publication Style Guide and Hashnode contributor workflow. Use when the user asks to "write freecodecamp style", "fCC tutorial", "freeCodeCamp style guide", "Hashnode draft for freeCodeCamp", "review this for freecodecamp", "fCC headline", "submit to freeCodeCamp editorial", "freeCodeCamp handbook", or mentions freeCodeCamp /news publication style, dual-submit (Submit Article + email draft URL), or MathJax tag requirements.

Curated code style patterns, idioms, and conventions drawn from popular GitHub developers and respected open source contributors (starting with shadcn, sindresorhus, and ahmadawais). Use this when you want to apply real-world community-proven patterns (e.g. "shadcn style", "write like shadcn", "shadcn/ui patterns", "sindresorhus style", "Sindre Sorhus patterns", "tiny elegant utilities", "ahmadawais style", "Ahmad Awais CLI patterns", "WordPress CLI workflows"), author or maintain collections of such styles, get before/after examples, or decide when a popular pattern is appropriate. Also activates for mentions of "patterns from popular github users", "community code styles", "hero patterns", "open source style guides", "authoring code styles", "shadcn", "sindresorhus", "ahmadawais", or specific developer names + style.

Pragmatic 80/20 guide to functional programming in TypeScript with fp-ts, drawing from Functional-Light JavaScript principles. Master pipe, Option, Either, map, and flatMap — and know exactly when to skip FP entirely for readable, "reasonable" code. Use this skill for a pragmatic starting point for fp-ts or functional programming in TypeScript, when the task is exploratory or educational and needs the 80/20 view of what is actually worth adopting, deciding if FP helps or hurts readability, replacing defensive null checks and try-catch with Option/Either, or getting before-and-after refactors for real code. Also activates for questions about "pragmatic functional programming", "fp-ts pipe Option Either", "when not to use functional programming", "80/20 fp-ts", "functional light", "FLJS", "reasonable code", "Kyle Simpson FP", or "pragmatic fp in TypeScript".

Route tasks and route the user to the correct devex-kit skill before any work begins. Use when starting conversations or tasks that may involve documentation contributions, writing style, cookbook quality, sidebar navigation, SDK design/build/ship, CLI or API tooling, MCP server craft, pragmatic code patterns and idioms (e.g. functional programming in TypeScript), agent plugin or skill development, devrel storytelling, DX first-success and content taxonomy, or when the user says "using devex-kit", "which devex-kit skill should I use", "help me pick the right skill from the kit", "route this to the right devex skill", or is unsure which /docs-* /sdk-* /mcp-* /devrel-* skill applies. Activates at the start of relevant sessions just like using-superpowers.

Design DX for first success and adoption, choose the right content types (Sample Applications, Code Snippets/Recipes, Solution Patterns), apply "content has a job" and translator principles, and run an effective technical engagement system. Use when working on getting-started experiences, sample apps vs recipes vs patterns decisions, content strategy, onboarding, or DX audits for developer-facing products. Also activates for mentions of "first success", "sample applications", "code snippets", "recipes", "solution patterns", "dx journey", "onboarding", "content has a job", "translator", "share knowledge not features", "technical engagement system", or "dev gtm".

Design authentic stories, recruit and run Technical Advisory Boards (TAB), avoid the 12 most common story mistakes, build dev influencer presence, and define dev-friendly packaging, pricing, and feedback loops for early-stage developer-facing products and startups. Use when working on GTM positioning, launch narratives, TAB outreach, presence strategy, or packaging for devs. Also activates for mentions of "story", "TAB", "12 most common story mistakes", "villain", "sell the category", "authenticity", "presence", "packaging", "pricing for devs", "manager deadline", "ship tonight", "launch story", or "dev gtm".

Diagnose and fix documentation quality problems in cookbook-style writing — skimmability, writing clarity, and reader helpfulness.

Route documentation contributions to the right content type, placement, template, and escalation path — before the contributor writes a single line.