# Project Design

> Design phase for {PROJECT} — data model, module boundaries, API contract, access control, and any multi-tenancy/security design, before code is written. Called by project-orchestrator before implementation; also used directly when the user says "design {PROJECT}'s X module.

- **Type:** Skill
- **Install:** `agentstack add skill-cormff-claude-code-playbook-project-design`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [cormff](https://agentstack.voostack.com/s/cormff)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [cormff](https://github.com/cormff)
- **Source:** https://github.com/cormff/claude-code-playbook/tree/main/skill-tree/layer-2-orchestrator/project-design

## Install

```sh
agentstack add skill-cormff-claude-code-playbook-project-design
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# {PROJECT} Design

Produces the design artifacts that [`project-implement`](../project-implement/SKILL.md) will build against, and records any durable architectural decision.

## Produce

1. **Data model** — entities, relationships, and any project-wide invariants (e.g. tenant scoping, required indexes).
2. **Module boundaries** — what this module owns, what it exposes to (and consumes from) other modules.
3. **API contract** — request/response shapes, or an OpenAPI-style spec if the project already uses one.
4. **Access control** — who/what can do what.
5. **Cross-cutting concerns**, if relevant — multi-tenancy isolation, security constraints.

## Recording decisions

Any decision that would be expensive to silently reverse later (a schema choice, a boundary, a naming convention applied project-wide) goes into `Decisions.md` (see [`project-orchestrator`](../project-orchestrator/SKILL.md#workspace-fill-in-with-real-paths)) as a short ADR: context, decision, why, alternatives considered. Anything already locked there is a constraint on this design, not a fresh choice — flag it as the "genuinely critical decision" stop condition in the orchestrator if a real conflict comes up.

## Output

A design note under the module's vault folder, structured so [`project-implement`](../project-implement/SKILL.md) can build directly from it without re-deriving decisions that were already made here.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [cormff](https://github.com/cormff)
- **Source:** [cormff/claude-code-playbook](https://github.com/cormff/claude-code-playbook)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-cormff-claude-code-playbook-project-design
- Seller: https://agentstack.voostack.com/s/cormff
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.
