Loading...
Loading...
Found 9,641 Skills
Plan-then-execute implementation against SPEC.md. Native single-thread loop, no sub-agents. On test or build failure, auto-invokes the backprop skill before retrying — a failed verification always considers whether a new §V invariant would prevent recurrence. Triggers when the user asks to build, implement, execute the spec, or tackle a specific §T task (`build §T.3`, `build --next`, `implement next task`, `run the build`). Expects SPEC.md to exist; if not, defers to the spec skill.
Initialize a new project — repo, structure, CI, and first commit
Acts as a Senior Staff Engineer to enforce high-quality software development standards. Use this skill when the user asks for code implementation, architectural review, debugging, or technical design. It ensures all code is production-ready, typed, and architecturally sound.
Diagnose GitHub bug reports in openai/codex. Use when given a GitHub issue URL from openai/codex and asked to decide next steps such as verifying against the repo, requesting more info, or explaining why it is not a bug; follow any additional user-provided instructions.
Create a pull request with Conventional Commits formatting, a templated body, and local verification. Use when the user asks to create a PR, open a PR, submit changes for review, or put code up for review.
Holistic, system-aware planning before implementing non-trivial tasks. Use when the task involves new features, architectural decisions, multi-file changes, unclear requirements, or multiple valid approaches. Triggers on "/plan", "plan this", "design an approach", "let's plan first".
PRD/Requirement Document Anti-Omission Assistant. When a user provides a requirement document (PRD, functional specification, product document, etc.) and requests to generate front-end pages, implement functions, or carry out development, this Skill must be used first to convert the requirement document into a structured Checklist, then implement code module by module to prevent function omissions. Trigger scenarios: The user sends a .md/.docx/.pdf requirement document and asks you to "generate pages", "implement functions", "write code", "develop this system"; the user says "develop according to this PRD", "generate based on the requirement document", "implement this document"; the user provides a requirement description of more than 200 lines. Even if the user does not mention the checklist, this process should be automatically triggered if the input is a long requirement document (>200 lines) and the goal is to generate code.
Manage app translations with goman.live. Use when: adding translations, adding i18n keys, localizing components, checking translation keys exist, searching translations, updating language content, managing i18n strings, extract hardcoded strings, localize folder, audit missing translations.
Use when acting as Grunk - reads specs from beads, plans, implements, commits, tags pr-ready. Merged TL+Engineer. Works in loop mode or interactive mode.
Ann — Master Orchestrator for MEL/SRHR work. Use when Ane brings any analytical, evaluation, SRHR, or structured-output task. Ann classifies task complexity, queries the MEL Wiki, retrieves knowledge, creates an implementation plan (verifies with user for complex tasks), delegates to Vi for execution, runs a 5-point quality gate, and delivers. General-purpose — not tied to any specific project.
Single-file horizontal-swipe slide deck for a weekly team update — shipped, in flight, blocked, metrics, asks. 6–8 slides. Use when the brief mentions "weekly update", "team update slides", "weekly status", "周报演示".
Use when implementation is complete, tests pass, and code needs to reach main — via PR with auto-merge (CI up) or local shallow-clone merge (CI down)