writing-shape
vmain
io.github.vinvcn/mattpocock-skills-zh-CN/writing-shape
通过对话会话,把一份原始素材 Markdown 文件塑造成文章:起草候选开头,逐段扩展,并在每一步讨论格式(列表、表格、提示块、引用)。适用于用户有一堆笔记、片段或粗稿,并希望把它变成可发布作品时。
“writing” 共 661 个结果
vmain
io.github.vinvcn/mattpocock-skills-zh-CN/writing-shape
通过对话会话,把一份原始素材 Markdown 文件塑造成文章:起草候选开头,逐段扩展,并在每一步讨论格式(列表、表格、提示块、引用)。适用于用户有一堆笔记、片段或粗稿,并希望把它变成可发布作品时。
vmain
io.github.nexu-io/open-design/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.crbnos/carbon/writing-skills
House guide for creating or editing agent skills in this repo (.ai/skills/). Use when writing a new skill, restructuring an existing one, or reviewing skills for quality. Covers the frontmatter contract, the install wiring, the house template, and the weak-executor writing rules every Carbon skill follows.
vmaster
io.github.nukeop/nuclear/writing-plugins
Use when writing, scaffolding, or modifying Nuclear plugins. Covers plugin structure, manifest, entry point, provider types, available APIs, and publishing. Trigger phrases include "create a plugin", "write a plugin", "plugin scaffold", "streaming provider", "metadata provider".
vdevelop
io.github.handsontable/handsontable/writing-docs-pages
Use when creating or editing documentation pages in docs/content/guides/ - covers YAML frontmatter, page structure, framework-specific example embedding, writing style, and sidebar registration
vmain
io.github.code-yeongyu/lazycodex/writing-design-plans
Use when you have a design brief or strategy and need to break implementation into reviewable chunks — creates step-by-step plans with verification criteria for each task
vmain
io.github.Klotzkette/claude-fuer-deutsches-recht/writing-dokumente-intake
Dokumentenintake: sortiert Dokumente, erkennt Lücken, ordnet Beweiswert und formuliert gezielte Rückfragen.
vmain
io.github.TriliumNext/Trilium/writing-unit-tests
Use when writing, extending, or debugging Vitest unit tests anywhere in the Trilium monorepo — Preact components, jQuery widgets, client services, or the server/trilium-core backend. Covers how to render components (zero new deps), the easy-froca/becca fixtures, supertest API patterns, the honest coverage config, running a single test, and the known gotchas.
vmain
io.github.marin-community/marin/writing-style
Marin house writing style. Use when drafting or revising Marin-authored prose.
vmain
io.github.sickn33/antigravity-awesome-skills/writing-skills
Use when creating, updating, or improving agent skills.
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.