/templates
Knowledge-base document templates, loaded when long-lived knowledge files are created or materialized.
$ npx -y skills add evidentloop/sopify --skill templates --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
- You can call itInvoke it directly when you want it.
- Slash command
/templates
Context preview
The summary Claude sees to decide when to auto-load this skill.
Knowledge-base document templates, loaded when long-lived knowledge files are created or materialized.
SKILL.md
templates.SKILL.mdname: templates
description: Knowledge-base document templates, loaded when long-lived knowledge files are created or materialized.
Knowledge Base Templates
The Templates skill defines stable knowledge-base document structures. It does not decide when to write, how to apply `knowledge_sync`, or how a plan moves through its lifecycle.
- For knowledge-base policy and `knowledge_sync`, read the `kb` skill.
- For `light / standard / architecture` levels and plan-body templates, read Design `assets/`.
- For active-plan, handoff, and receipt reads and writes, follow the governing Protocol.
Replace placeholders and remove empty optional sections. Do not store one-off implementation detail as long-lived knowledge.
`project.md`
# Project Conventions
## Technology
- Core: {language or framework version}
- Build: {build tool}
- Test: {test framework}
## Conventions
- {reusable technical convention}
## Document boundaries
- `project.md`: technical conventions
- `blueprint/background.md`: long-term goals, scope, and non-goals
- `blueprint/design.md`: module, host, directory, and consumption contracts
- `blueprint/tasks.md`: unfinished long-term work and explicit deferrals`blueprint/README.md`
# Project Blueprint Index
Status: {current status}
Maintenance: keep only status, current goal, current focus, and reading links
## Current goal
- {long-term goal summary}
## Current focus
- Active plan: {none / link to plan.md}
- Archive status: {status}
## Read next
- [Project conventions](../project.md)
- [Background](./background.md)
- [Design](./design.md)
- [Tasks](./tasks.md)
- [History](../history/index.md)List each long-lived topic document in “Read next” when the `blueprint/` root contains one.
`blueprint/background.md`
# Blueprint Background
## Long-term goals
- {goal}
## Scope
- In scope: {content}
- Out of scope: {content}
## Non-goals
- {content}`blueprint/design.md`
# Blueprint Design
## Governing contracts
- {contract that remains valid across plans}
## Module and consumption boundaries
- {module, host, or directory responsibility}`blueprint/tasks.md`
# Blueprint Tasks
## Unfinished long-term work
- [ ] {item}
## Explicit deferrals
- [-] {item and revisit condition}Keep only unfinished long-term work and explicit deferrals. Remove `[x]` items.
`history/index.md`
# Change History Index
| Date | Feature | Status | Plan package |
|------|---------|--------|--------------|
| {YYYY-MM-DD} | {feature} | {status} | [link](YYYY-MM/...) |`user/preferences.md`
# Long-term User Preferences
- {explicit preference that applies across tasks}`user/feedback.jsonl`
{"timestamp":"{ISO-8601}","source":"chat","message":"{raw feedback}","scope":"{scope}","promote_to_preference":false}Read more
name: templates description: Knowledge-base document templates, loaded when long-lived knowledge files are created or materialized.
Knowledge Base Templates
The Templates skill defines stable knowledge-base document structures. It does not decide when to write, how to apply `knowledge_sync`, or how a plan moves through its lifecycle.
- For knowledge-base policy and `knowledge_sync`, read the `kb` skill.
- For `light / standard / architecture` levels and plan-body templates, read Design `assets/`.
- For active-plan, handoff, and receipt reads and writes, follow the governing Protocol.
Replace placeholders and remove empty optional sections. Do not store one-off implementation detail as long-lived knowledge.
`project.md`
# Project Conventions
## Technology
- Core: {language or framework version}
- Build: {build tool}
- Test: {test framework}
## Conventions
- {reusable technical convention}
## Document boundaries
- `project.md`: technical conventions
- `blueprint/background.md`: long-term goals, scope, and non-goals
- `blueprint/design.md`: module, host, directory, and consumption contracts
- `blueprint/tasks.md`: unfinished long-term work and explicit deferrals`blueprint/README.md`
# Project Blueprint Index
Status: {current status}
Maintenance: keep only status, current goal, current focus, and reading links
## Current goal
- {long-term goal summary}
## Current focus
- Active plan: {none / link to plan.md}
- Archive status: {status}
## Read next
- [Project conventions](../project.md)
- [Background](./background.md)
- [Design](./design.md)
- [Tasks](./tasks.md)
- [History](../history/index.md)List each long-lived topic document in “Read next” when the `blueprint/` root contains one.
`blueprint/background.md`
# Blueprint Background
## Long-term goals
- {goal}
## Scope
- In scope: {content}
- Out of scope: {content}
## Non-goals
- {content}`blueprint/design.md`
# Blueprint Design
## Governing contracts
- {contract that remains valid across plans}
## Module and consumption boundaries
- {module, host, or directory responsibility}`blueprint/tasks.md`
# Blueprint Tasks
## Unfinished long-term work
- [ ] {item}
## Explicit deferrals
- [-] {item and revisit condition}Keep only unfinished long-term work and explicit deferrals. Remove `[x]` items.
`history/index.md`
# Change History Index
| Date | Feature | Status | Plan package |
|------|---------|--------|--------------|
| {YYYY-MM-DD} | {feature} | {status} | [link](YYYY-MM/...) |`user/preferences.md`
# Long-term User Preferences
- {explicit preference that applies across tasks}`user/feedback.jsonl`
{"timestamp":"{ISO-8601}","source":"chat","message":"{raw feedback}","scope":"{scope}","promote_to_preference":false}Resumable AI coding — ask first, plans stay with the repo AI coding tools are fast. But when they jump to code before the facts are clear, speed turns into rework.
Other skills on sopify.
- /analyze
Analyze phase entry. Aggregates scoring, follow-up, and scope-check rules; loads references/assets/scripts on demand.
Open skill - /design
Design phase entry. Aggregates plan-level selection, task breakdown, and package output rules; loads references/assets/scripts on demand.
Open skill - /develop
Develop phase entry; routes task execution, state updates, KB sync, and plan close-out through references/assets/scripts.
Open skill - /kb
Manage long-lived `.sopify/` knowledge, including bootstrap, progressive materialization, reads, retention, and knowledge_sync policy.
Open skill - /analyze
需求分析阶段入口;聚合评分、追问与范围判定规则,按需加载 references/assets/scripts。
Open skill - /design
方案设计阶段入口;聚合方案分级、任务拆分与方案包输出规则,按需加载 references/assets/scripts。
Open skill

