Sight
DesignsightSight is an Agent Skill for design published in the cwinvestments/memstack repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Use when the user says 'draw', 'diagram', 'visualize', 'architecture', or needs a visual overview of code structure.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/cwinvestments/memstack/blob/HEAD/skills/sight/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sight, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
šļø Sight ā The Hidden Becomes Clear
Generate Mermaid diagrams showing project architecture, schema, and data flow.
Activation
When this skill activates, output:
šļø Sight ā The hidden becomes clear.
Then execute the protocol below.
Context Guard
| Context | Status |
|---|---|
| User asks for a diagram or visualization | ACTIVE ā generate diagram |
| User says "draw", "diagram", "architecture" | ACTIVE ā generate diagram |
| User asks to "show" or "map" the structure | ACTIVE ā generate diagram |
| Discussing diagrams conceptually | DORMANT ā do not activate |
| User is looking at existing diagrams | DORMANT ā do not activate |
Protocol
-
Determine diagram type from context:
- "database" / "schema" ā
erDiagram - "api" / "endpoints" ā
flowchart TD - "components" / "pages" ā
graph TD - "architecture" / "structure" ā
flowchart TD(system overview) - "flow" / "process" ā
sequenceDiagram
- "database" / "schema" ā
-
Scan the relevant code:
- For DB: read migration files in
database/ - For API: list files in
src/app/api/ - For pages: list files in
src/app/ - For architecture: read package.json, directory structure, configs
- For DB: read migration files in
-
Generate Mermaid diagram as a code block
-
Optionally save to
docs/diagrams/{name}.mermaid
Inputs
- What to visualize (database, API, components, architecture)
- Project directory
Outputs
- Mermaid diagram code block ready to render
- Optional saved .mermaid file
Example Usage
User: "draw the AdminStack database schema"
šļø Sight ā The hidden becomes clear.
ā```mermaid
erDiagram
accounts ||--o{ organizations : "has"
accounts ||--o{ cc_sessions : "tracks"
organizations ||--o{ projects : "contains"
organizations ||--o{ contacts : "stores"
organizations ||--o{ orders : "processes"
accounts {
uuid id PK
text email
boolean is_platform_admin
}
cc_sessions {
uuid id PK
text name
text status
}
ā```
Level History
- Lv.1 ā Base: Mermaid diagram generation from codebase analysis. (Origin: MemStack v1.0, Feb 2026)
- Lv.2 ā Enhanced: Added YAML frontmatter, context guard, activation message, diagram type detection. (Origin: MemStack v2.0 MemoryCore merge, Feb 2026)