菜单
Tell the agent to zoom out and give a higher-level map of an unfamiliar area of the @flow-state-dev codebase, named in FSD vocabulary. Use when you've just landed in an area and want the lay of the land before touching anything.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Create a new persistence store adapter package implementing all StoreRegistry interfaces. Produces a complete package with factory, individual stores, schema initialization, and tests.
Add a new page to the flow-state-dev documentation site (Docusaurus). Handles frontmatter, sidebar placement, content structure, and cross-linking.
Create a new flow definition with actions, scopes, resources, and capabilities. Produces the flow file, action blocks, and server registration.
Create a new block (handler, generator, utility, or router) following project conventions. Produces the block file, exports, and a matching test file.
Create a Linear issue for work already done (or in progress), check out a fix/ branch, commit the changes, and open a PR. For quick logging and shipping of on-the-fly work.
Create a new composable pattern — a multi-block sequencer composition that solves a recurring agentic architecture problem. Produces the pattern factory, internal blocks, tests, and documentation.
| name | fsd:zoom-out |
| description | Tell the agent to zoom out and give a higher-level map of an unfamiliar area of the @flow-state-dev codebase, named in FSD vocabulary. Use when you've just landed in an area and want the lay of the land before touching anything. |
| disable-model-invocation | true |
I don't know this area well. Zoom out and give me a map.
Use FSD vocabulary for everything you name:
@flow-state-dev/<pkg>) and its role in the layered architecture (core / server / client / react / cli / testing / store-* / patterns / capabilities / memory / ui / etc.)server↔client or client↔react? Where are the seams?Cross-reference the relevant docs/architecture/<area>.md doc as the authoritative reference for any contract you describe.
Keep the map terse — a list of named things and one-line roles, not prose paragraphs. The point is to give me an index I can jump from, not a tutorial.