writing-plans
vmain
io.github.proma-ai/Proma/writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
“writing” 共 494 个结果
vmain
io.github.proma-ai/Proma/writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
vmain
io.github.mohitagw15856/pm-claude-skills/writing-great-skills
Author a high-quality Agent Skill (SKILL.md) that an AI reliably triggers and executes well — strong frontmatter, a sharp description with trigger phrases, a clear output contract, quality checks, and anti-patterns. Use when asked to write a skill, create a SKILL.md, improve a skill, review a skill for quality, or contribute to a skills library. Produces a complete, SkillCheck-passing SKILL.md plus a short rationale for the key choices.
vmain
io.github.runceel/ReactiveProperty/writing-mstest-tests
Best practices for writing new MSTest 3.x/4.x unit tests and implementing concrete fixes in existing MSTest code. Use when the user asks to write, create, implement, repair, or modernize tests (including fix-it prompts such as 'something seems off, fix issues'). Primary fit for direct code changes like correcting swapped Assert.AreEqual argument order, replacing outdated assertion patterns, and converting DynamicData from IEnumerable<object[]> to ValueTuple-based data sets. Covers modern assertions, data-driven tests, test lifecycle, MSTest.Sdk, sealed classes, Assert.Throws, DynamicData with ValueTuples, TestContext, and conditional execution. Do NOT use for broad test quality audits, flaky-test investigations, or test smell detection reports — use test-anti-patterns instead.
vmain
io.github.sickn33/antigravity-awesome-skills/writing-great-skills
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
vmain
io.github.marmelab/atomic-crm/writing-migrations
Generate Supabase SQL migrations at deploy time from the session branch diff. Used by simple-developer in the deploy-time migration round only.
vmaster
io.github.actualbudget/actual/writing-actual-docs
Use whenever creating, updating, editing, drafting, restructuring, or fixing documentation in the Actual Budget repo — specifically anything under `packages/docs/` (the Docusaurus site published at actualbudget.org/docs) or any change to `.md` / `.mdx` files in that package. Trigger for asks like "add a doc page for X", "update the FAQ", "write a guide for the new feature", "document this setting", "fix the docs about Y", "add a contributing page", or any work on the docs site, even when the user does not explicitly mention style, structure, or conventions. Actual's docs follow strict Docusaurus conventions (front matter, heading levels, image placement and naming, admonition syntax, Title Case, tone of voice, spelling allowlist) and writing them without consulting the project's style guide reliably produces output that fails review and needs to be redone.
vmain
io.github.GCWing/BitFun/writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment
vmain
io.github.zts212653/clowder-ai/writing-plans
将 spec/需求拆分为可执行的分步实施计划。 Use when: 有 spec 或需求,准备动手前需要拆分步骤。 Not for: trivial 改动(≤5 行)、已有详细计划。 Output: 分步实施计划(含 TDD 步骤和检查点)。
vmain
io.github.zts212653/clowder-ai/writing-skills
创建或修改 Cat Café skill / MCP tool description 的元技能(含质量标准、范本、发布)。 Use when: 写新 skill、修改现有 skill、写/改 MCP tool description、验证 skill 质量; 或者功能实现中产出了 SKILL.md / cat-cafe-skills/ 新目录 / manifest.yaml skill 条目。 Not for: 使用 skill(直接触发对应 skill)。 Output: 新/更新的 SKILL.md + manifest 条目 + symlinks。 GOTCHA: 软硬同重——skill/MCP 质量 = 代码质量;不要写模型已知的通用教程,先过价值门禁。
vmain
io.github.jnMetaCode/superpowers-zh/writing-skills
当创建新技能、编辑现有技能或在部署前验证技能是否有效时使用
vmain
io.github.jnMetaCode/superpowers-zh/writing-plans
当你有规格说明或需求用于多步骤任务时使用,在动手写代码之前
vmaster
io.github.onsi/ginkgo/writing-specs
Author good Ginkgo specs — container nodes (Describe/Context/When), subject nodes (It/Specify), setup/cleanup nodes (BeforeEach, JustBeforeEach, AfterEach, DeferCleanup, BeforeSuite/AfterSuite), the "declare in container, initialize in BeforeEach" rule, separating creation from configuration, reusable test helpers with GinkgoHelper()/GinkgoHelperGo(), and By/GinkgoWriter output. Use when writing or reviewing specs or extracting a test helper. Covers the tree-construction-time pitfalls (no assertions/init/loop-capture in container bodies).
vmain
io.github.Klotzkette/claude-fuer-deutsches-recht/writing-unterlagen-luecken
Unterlagen und Lücken: sortiert Dokumente, erkennt Lücken, ordnet Beweiswert und formuliert gezielte Rückfragen.
vmain
io.github.Klotzkette/claude-fuer-deutsches-recht/writing-einstieg-routing
Einstieg und Routing: klärt Rolle, Ziel, Frist, Aktenlage und den passenden nächsten Fachpfad.
vmain
io.github.affaan-m/ECC/article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
vmain
io.github.pcvelz/superpowers/writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
vdevelop
io.github.strapi/strapi/writing-a-skill
Create a new agent skill with progressive disclosure and bundled resources. Use when the user wants to create, write, or build a new skill.
vmaster
io.github.flutter/flutter/natural-writing
Contains well-defined rules for creating natural, accurate, and readable writing. Use whenever authoring longer text, like analysis documents, PR or CL descriptions, or documentation.
vmain
io.github.millionco/react-doctor/writing-guidelines
Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".
vmain
io.github.a5c-ai/babysitter/writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
vmain
io.github.a5c-ai/babysitter/writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code. Creates bite-sized TDD implementation plans with dependency tracking.
vmain
io.github.microclaw/microclaw/writing-editor
Improve or write prose: tighten, clarify, fix grammar, and adjust tone/length while preserving the author's voice and meaning. Use when users ask to edit, proofread, rewrite, polish, shorten, or change the tone of text, or to draft something from notes. Triggers on mentions of edit, proofread, rewrite, polish, tighten, make it shorter/clearer/more formal, fix grammar, 润色, 改写, 校对, 修改, 精简, 改语气, 帮我写.
vmaster
io.github.PostHog/posthog/writing-clickhouse-queries
Guide for writing performant ClickHouse queries in PostHog product code. Use when writing HogQL query runners, designing a ClickHouse table for a new product, adding materialized columns or skip indexes, or choosing a row ID format. For optimizing an existing query that is already too slow, use `/optimizing-clickhouse-and-hogql-queries` instead.
vmain
io.github.vercel-labs/agent-skills/writing-guidelines
Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook".