Loading...
Loading...
Found 26 Skills
Activate to orchestrate multi-phase design projects, set briefs, enforce quality gates, and sequence specialist work.
Global writing style specification for Chinese technical writing. Applicable to all Chinese content production (WeChat Official Accounts, blogs, X, knowledge bases, AIW). Cited by gracker-writer and content-quality-gate.
Verify claims in generated output against sources. Use as a separate pass AFTER content generation to catch hallucinations. Critical constraint - cannot be reliably combined with generation in a single pass.
Verification discipline for completion claims. Use when about to assert success, claim a fix is complete, report tests passing, or before commits and PRs. Enforces evidence-first workflow.
A skill for creating note articles in the interview format of kimny × Claude (AI). It defines release judgment rules based on quality gates (discovery, external anchor, one-sentence test), AIO optimization specifications, and dialogue format rules. Usage scenarios: (1) Creation and rewrite of note articles (2) Structuring interview-style articles (3) Converting historical conversations into articles (4) Article quality check. Example triggers: "I want to turn this into an article", "I want to write on note", "Use interview format", "Can this be made into an article?", "Rewrite the article", "Pass the quality gate", "AIO optimization", "note article"
Trigger: Called when a task is completed, enters phase acceptance, receives critical feedback, or repeated similar errors require systematic correction; common signals include review, audit, retrospective, quality check, error correction and retrospective. Trigger after delivery or at a review checkpoint when quality must be examined honestly and errors must be corrected without defensiveness. Use this skill for structured self-review, feedback processing, and continuous correction.
Implement Statistical Process Control charts to monitor production process stability. Use this skill when the user needs to detect process shifts, set control limits, or distinguish common cause from special cause variation — even if they say 'process monitoring', 'control chart', or 'is our process in control'.
Evaluate every produced output (code, report, plan, data, API response) against type-specific quality criteria, score 1-10, make accept/reject decisions, and provide actionable improvement suggestions. Triggers on "evaluate", "check", "review", "quality control", "is this good enough", "score it", or before passing output to the next step in an agentic workflow.
Claiming work is complete without verification is dishonesty, not efficiency. Use when ANY variation of success/completion claims, ANY expression of satisfaction, or ANY positive statement about work state.
Пополняет существующий memory bank постоянными знаниями проекта. Используй, когда пользователь явно просит запомнить проектное решение, сохранить сведения в базе знаний, обновить постоянную проектную спецификацию или добавить материал в memory bank. Не используй для спецификаций результата и планов в `changes/`, временного контекста, личных предпочтений или создания memory bank с нуля.
Создаёт однозначную спецификацию результата без шагов реализации. Используй, когда пользователь хочет зафиксировать контекст задачи, обоснование правки, желаемый итог, критерии приемки и рамки, оставив технический путь исполняющему агенту. Не используй для выбора решения, составления плана реализации, непосредственной реализации или ревью изменений кода.
Создаёт memory bank проекта с нуля и выполняет его первичное заполнение. Используй только при явном вызове /bro-init-memory-bank, когда пользователь хочет создать новый банк знаний проекта. Не используй для пополнения существующего memory bank или сохранения отдельного проектного решения.