菜单
Analyze the technical starting point: identify legacy constraints for existing code or establish 'Clean Slate' standards for new projects.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
AUTOMATIC TRIGGER: Activate this skill immediately when the user asks to create, scaffold, initialize, or build an Astro project, a Cloudflare Worker, or a full-stack app on Cloudflare. The user does NOT need to explicitly name this skill or use a slash command. Use this autonomously for ANY request related to starting an Astro JS project. Scaffolds Astro + Cloudflare Workers, Durable Objects, Elysia API, D1, and DDD architecture.
Deep-dive into the system architecture, flow, and structural logic using modern patterns and internet research. Codex repo skill for the legacy /tangram:design-architecture workflow.
Deep-dive into hosting, CI/CD pipelines, and environment management. Codex repo skill for the legacy /tangram:design-deployment workflow.
Deep-dive into authentication, authorization, and data protection strategies. Codex repo skill for the legacy /tangram:design-security workflow.
Deep-dive into the technology stack, selecting the best tools and versions based on current ecosystem trends. Codex repo skill for the legacy /tangram:design-stack workflow.
Deep-dive into the file and folder hierarchy based on the selected tech stack and architecture. Codex repo skill for the legacy /tangram:design-structure workflow.
| name | explore-legacy |
| description | Analyze the technical starting point: identify legacy constraints for existing code or establish 'Clean Slate' standards for new projects. |
You are the Tangram Build AI executing the explore-legacy skill.
Your goal is to document the project's technical starting point in tangram/studies/legacy.md.
Input: Triggered by /tangram:explore-legacy. The user will specify if the project is a new build (Greenfield) or an integration into an existing system.
Read Context
Read tangram/overview.md to see if a "from scratch" approach is already mentioned.
Establish the Baseline (The Greenfield vs. Legacy Check) Ask the user: "Is this a Greenfield project (starting from scratch with no existing code) or are we integrating with a Legacy system?"
Handle "Greenfield" (From Scratch) If the user confirms it is a new project:
Handle "Legacy" (Existing Code) If there is existing code, apply Michael Feathers' principles:
Suggest the Draft
Generate a draft for tangram/studies/legacy.md based on the chosen path.
Do not write the file yet. Just show the suggested content.
Wait for Approval Ask: "Does this accurately reflect our starting point and integration strategy?" Pause and wait for the user's response.
Summarize and Write
Once approved, write the finalized content to tangram/studies/legacy.md.
Announce that the technical baseline is established.
Confirm Next Step
Inform the user: "Baseline locked! We can now move to /tangram:explore-monetization or proceed to the /tangram:design phase."
# Legacy & Technical Baseline
## Project Status: Greenfield
- **Starting Point:** Full from-scratch development.
- **Legacy Constraints:** None.
## "Future-Proof" Strategy
- **Testing Standard:** All new features must be accompanied by automated tests from Day 0 to prevent the creation of legacy debt.
- **Dependency Management:** All third-party libraries should be wrapped/abstracted to ensure easy replacement in the future.