Skip to content
FunCoding

Search

Search docs, Skills and MCP

trellis-spec-bootstrap

Bootstrap project-specific Trellis coding specs with a platform-neutral single-agent workflow. Use when creating or refreshing .trellis/spec guidelines, analyzing a codebase with GitNexus, ABCoder, or source inspection, decomposing package/layer spec work, and writing real codebase-backed spec docs without placeholder text.

文档与办公1.8k.cursor/skills/trellis-spec-bootstrap/SKILL.md

Install

Send this to Claude Code, Codex or Cursor. The agent checks the Skill for safety first and installs it only after you confirm.

读取 https://funcoding.ai/skills/fy-agent/fyagent/cursor-skills-trellis-spec-bootstrap/install.md ,按里面的步骤帮我安装这个 Skill。

SKILL.md

Trellis Spec Bootstrap

Use this skill to create or refresh .trellis/spec/ guidelines from the real codebase. One capable agent owns the full loop: analyze the repository, choose the spec boundaries, write the docs, and verify the result. The workflow does not depend on a specific host, CLI, or agent brand.

Workflow

  1. Confirm Trellis is initialized and inspect the current .trellis/spec/ tree.
  2. Analyze the repository architecture with the best available tools: GitNexus, ABCoder, language tooling, and direct source reads.
  3. Decompose the spec work by package and layer only when that reflects the actual codebase.
  4. Fill or reshape the spec files with concrete patterns, file paths, examples, and anti-patterns from the project.
  5. Verify that the final specs are internally consistent and contain no template placeholders.

Reference Routing

NeedRead
Repository architecture analysisreferences/repository-analysis.md
Spec work decomposition and task planningreferences/spec-task-planning.md
Writing high-signal Trellis spec filesreferences/spec-writing.md
GitNexus and ABCoder MCP setupreferences/mcp-setup.md

Operating Rules

  • Treat templates as starting points, not contracts. Delete, rename, split, or add spec files when the repository calls for it.
  • Prefer source-backed rules over generic advice. Every important recommendation should point at a real file or repeated local pattern.
  • Keep execution single-owner by default. Optional helper agents are an implementation detail, not a requirement or user-visible dependency.
  • Do not write platform-specific instructions unless the target project already standardizes on that platform.
  • Do not leave placeholder text, empty headings, or copied boilerplate in .trellis/spec/.

Done Criteria

  • .trellis/spec/ describes the project as it exists now.
  • Each relevant package or layer has practical coding guidance with real examples.
  • Non-applicable template sections are removed.
  • index.md files match the final spec file set.
  • Any required setup or analysis assumptions are documented in the relevant spec or task notes.

Similar Skills

pdf
anthropics/skills180k

pdf

Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms, encrypting/decrypting PDFs, extracting images, and OCR on scanned PDFs to make them searchable. If the user mentions a .pdf file or asks to produce one, use this skill.

Docs & office

discernment-nudge
anthropics/skills180k

discernment-nudge

After you give a substantive answer or draft that the user may act on — advice or recommendations, drafted artifacts such as goals, plans, pitches, proposals, or emails, estimates or projections, analysis or interpretation of data, factual claims they may rely on, or a multi-step argument — invoke this skill BEFORE finalizing your reply and then, if it applies, append 2-3 short follow-up questions, each tied to something specific in what you just produced, that help the user check key facts, probe the reasoning or assumptions, and notice missing context. Do this at most once per conversation. Skip it when the user asked a trivial how-to or simple lookup, wants a purely educational explanation, asked you only to format, convert, or assemble a file from content they provided, is writing code they will run, is doing creative writing or casual chat, or already asked you to double-check, cite, or review — the skill file explains these boundaries and the exact output format.

Docs & office

doc-coauthoring
anthropics/skills180k

doc-coauthoring

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

Docs & office

docx
anthropics/skills180k

docx

Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx or .dotx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.

Docs & office

pptx
anthropics/skills180k

pptx

Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates (.potx), layouts, speaker notes, or comments. Trigger whenever the user mentions "deck," "slides," "presentation," or references a .pptx or .potx filename, regardless of what they plan to do with the content afterward. If a .pptx or .potx file needs to be opened, created, or touched, use this skill.

Docs & office

canvas-design
anthropics/skills180k

canvas-design

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

Docs & office