OpenParable
Skip to content
← Back to skills

Sight

Design
sight

Sight 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.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
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

ContextStatus
User asks for a diagram or visualizationACTIVE — generate diagram
User says "draw", "diagram", "architecture"ACTIVE — generate diagram
User asks to "show" or "map" the structureACTIVE — generate diagram
Discussing diagrams conceptuallyDORMANT — do not activate
User is looking at existing diagramsDORMANT — do not activate

Protocol

  1. 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
  2. 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
  3. Generate Mermaid diagram as a code block

  4. 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)