Loading...
Loading...
Found 670 Skills
Maintain documentation for the ai-dev framework and ai-dev-skills collection. Use when code or skill changes affect documented behavior, commands, agents, plugins, version releases, repository structure, README content, or changelogs. Triggers: "update docs", "sync documentation", "update README", "update changelog", "documentation audit", "doc sync", "更新文檔", "同步文件", "文檔檢查", "/doc-updater".
Review the ECC (everything-claude-code) distribution list, which includes two modes: (A) Existing List Pruning: Analyze the overlap and quality between distribution.yaml.enabled and first-party ai-dev-skills, and output enabled_remove recommendations; (B) New Item Import Evaluation: Based on ecc-catalog.yaml and the scope of the last update, introduce newly added skills from ECC upstream, analyze applicable scenarios, and recommend whether to add them to enabled. Use when: (1) Evaluating whether the ECC distribution list needs pruning, (2) Deciding whether to import after ECC upstream adds new skills, (3) Wanting to generate an ecc-profile.yaml starter for end users, (4) Conducting regular reviews quarterly/semi-annually. Triggers: "Analyze ECC skill", "ECC overlap", "ECC list pruning", "ECC new items", "ECC upstream additions", "Should I import", "ecc analyze", "ecc new items review", "ecc profile starter", "ECC quality review".
Scout the current work and recommend the next skill or action. Arguments: repo (whole-repo health), issue (deep implementation plan for an issue), milestone (milestone readiness and issue set). With no argument, read git logs and local branch state first to set scope, then suggest what to do next. Use when the user asks to recon, scout, assess, or "what should I do next". Knows DecisionNerd/dev-skills: agents, architect-it, idk-now, kiss, repos, issues, milestones, pulls, check-readiness, merge-it, fix-it, test-it, observe-it, document-it, research-it, refactor-it, troubleshoot-app, diagnose-bug, tidy-up. Prefer idk-now when the user is lost or needs vision-tied coaching across DocSlime / ProductFeeling / Impeccable / vendored skills — not only this pack.
When the user doesn't know what to do next: briefly survey environment, repo, docs, and git history; guide them through clarifying questions; then suggest next steps using DecisionNerd/dev-skills plus DocSlime, ProductFeeling, Impeccable, and any vendored skills in the repo space — aimed at an achievable goal toward why the project exists. Use when the user says "idk", "I don't know", "what now", "stuck", "lost", or `/idk-now`. Prefer recon when they already know the domain and need a tactical next skill only.
Best practices for Remotion - Video creation in React
Best practices for rendering videos
Creating a new Remotion video
Dealing with captions in Remotion
Best practices for writing Remotion React Markup
Best practices for writing Remotion animations that stay intuitive for agents and editable in Remotion Studio Visual Mode.
Search and fetch Remotion documentation pages
Building video apps with Remotion - framework, rendering and Player advice