初始化
- 作者仓库星标 0
- 作者仓库 skills-registry
- 领域
- 人工智能
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @tomevault-io · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
## When this fires
User is at the start of a project (no `project-status.md`) or wants to bootstrap Matilha into an existing codebase. The skill scaffolds the minimum artifacts for Matilha to work: `project-status.md` with initial phase 0 state, `CLAUDE.md` / `AGENTS.md` / `GEMINI.md` as context primers, and the directory scaffold (`docs/matilha/`, `docs/superpowers/`).
## Preconditions
- Write access to cwd.
- No existing `project-status.md` unless user explicitly confirms overwrite.
## Execution Workflow
1. Verify preconditions via Bash `test -f project-status.md`. If present and user didn't say "force", ask the user before overwriting.
2. Prompt the user for `archetype` (one of: `saas-b2b`, `saas-b2c`, `frontend-only`, `cli`, `library`, `ml-service`, `marketplace`).
3. Compute ISO-UTC timestamp via Bash `date -u +%Y-%m-%dT%H:%M:%SZ`.
4. Write `project-status.md` via Write tool. Frontmatter shape: `schema_version: 1`, `name`, `archetype`, `created: <iso>`, `last_update: <iso>`, `current_phase: 0`, `phase_status: not_started`, `next_action: "Run /matilha-scout to enter Phase 10 discovery."`, `tools_detected: []`, `companion_skills: {impeccable: not_installed, shadcn: not_installed, superpowers: not_installed, typeui: not_installed}`, `active_waves: []`, `completed_waves: []`, `feature_artifacts: []`, `recent_decisions: []`, `pending_decisions: []`, `blockers: []`, `aesthetic_direction: null`, `design_locked: false`.
5. Write `CLAUDE.md` / `AGENTS.md` / `GEMINI.md` if absent (copy from this repo's templates if available via `matilha pull`, else from skeletons).
6. Create directories `docs/matilha/plans`, `docs/matilha/specs`, `docs/matilha/waves` via Bash `mkdir -p`.
7. Emit final message: "Initialized Matilha — current_phase: 0. Next: /matilha-scout".
## Rules: Do
- Respect explicit overwrite confirmation; do not silently clobber.
- Use ISO-UTC timestamps throughout.
- Create docs/ directories idempotently (skip if they exist).
## Rules: Don't
- Overwrite existing `project-status.md` without explicit user confirmation.
- Guess archetype from code (ask).
- Use local-time timestamps.
## Expected Behavior
On success, user has a Matilha-initialized project with the 3 context files + project-status.md. Next skill the user invokes is typically `matilha-scout` (Phase 10) or `matilha-plan` (Phase 20-30) if they already have research.
## Quality Gates
- `project-status.md` exists with valid frontmatter (conforms to `projectStatusSchema`).
- `docs/matilha/` directory tree exists.
- Context files (CLAUDE.md / AGENTS.md / GEMINI.md) exist.
- User can run `matilha-howl` next and see phase 0 state.
## Companion Integration
No companion integrations in Wave 4a. Future packs may extend this skill.
## Output Artifacts
- `project-status.md`
- `CLAUDE.md` (if absent)
- `AGENTS.md` (if absent)
- `GEMINI.md` (if absent)
- `docs/matilha/plans/`
- `docs/matilha/specs/`
- `docs/matilha/waves/`
## Example Constraint Language
- Use "must" for: project-status.md conforms to `projectStatusSchema`; ISO-UTC timestamps.
- Use "should" for: prompt interactively for archetype; skip overwrite of existing context files.
- Use "may" for: scaffold additional directories beyond the required ones if user requests.
## Troubleshooting
- **"project-status.md already exists"**: User confirms overwrite explicitly, or chooses a different directory.
- **"archetype not recognized"**: Must be one of `saas-b2b`, `saas-b2c`, `frontend-only`, `cli`, `library`, `ml-service`, `marketplace`; ask user to pick from the list.
## CLI shortcut (optional)
> If matilha CLI is installed (`matilha --version` succeeds), you can run
> `matilha init` to execute this deterministically. The plugin path
> above works without any CLI installation.
---
> Source: [danilods/matilha-skills](https://github.com/danilods/matilha-skills) — distributed by [TomeVault](https://tomevault.io).
<!-- tomevault:4.0:skill_md:2026-05-23 -->
章节与文件索引
按说明文件中的顺序排列。
当这个火起来的时候
前提条件
执行工作流程
规则:做
规则:不可以
文件/命令 -> project-status.md · CLAUDE.md · AGENTS.md · GEMINI.md · docs/matilha/ · docs/superpowers/ · test -f project-status.md · archetype
内容校验值 -> 08e45be42786
当前原文的自动摘译,尚未人工审校。
当这个火起来的时候
用户正处于项目开始阶段(无
project-status.md)或想要将 Matilha 引导到现有代码库中。该技能为 Matilha 工作提供了最少的工件:具有初始阶段 0 状态的project-status.md,作为上下文引物的CLAUDE.md/AGENTS.md/GEMINI.md,以及目录支架(docs/matilha/,docs/superpowers/)。前提条件
对 cwd 的写访问权限。除非用户明确确认覆盖,否则不存在现有的
project-status.md。执行工作流程
通过 Bash
test -f project-status.md验证先决条件。 如果存在并且用户没有说“强制”,则在覆盖之前询问用户。规则:做
尊重明确的覆盖确认;不要默默地破坏。始终使用 ISO-UTC 时间戳。幂等地创建文档/目录(如果存在则跳过)。
规则:不可以
无需用户明确确认即可覆盖现有的
project-status.md。从代码中猜测原型(提问)。使用本地时间时间戳。