Agent Skills: C3 Query - Architecture Navigation

|

UncategorizedID: lagz0ne/c3-skill/c3-query

Skill Files

Browse the full folder contents for c3-query.

Download Skill

Loading file tree…

skills/c3-query/SKILL.md

Skill Metadata

Name
c3-query
Description
|

C3 Query - Architecture Navigation

Navigate C3 docs AND explore corresponding code. Full context = docs + code.

REQUIRED: Load References First

  1. ../../references/skill-harness.md - Routing and red flags
  2. ../../references/layer-navigation.md - How to traverse C3 docs

Query Flow

Query → Clarify Intent → Navigate Layers → Extract References → Explore Code
              │
              └── Use AskUserQuestion if ambiguous

Step 0: Clarify Intent

Ask when:

  • Query vague ("how does X work?" - which aspect?)
  • Multiple interpretations ("authentication" - login? tokens? sessions?)
  • Scope unclear ("frontend" - whole container or specific component?)

Skip when:

  • Query includes C3 ID (c3-102)
  • Query specific ("where is login form submitted?")
  • User says "show me everything about X"

Step 1-2: Navigate and Extract

Follow layer navigation: Context → Container → Component

| Doc Section | Extract For Code | |-------------|------------------| | Component name | Class/module names | | ## References | Direct file paths, symbols | | Technology | Framework patterns | | Entry points | Main files, handlers |

Reference Lookup

If query relates to patterns/conventions:

  1. Check .c3/refs/ for ref-* matching topic
  2. Return ref content + citing components

Step 3: Explore Code

Use extracted references:

  • Glob: src/auth/**/*.ts
  • Grep: Class names, functions
  • Read: Specific files from ## References

Query Types

| Type | User Says | Response | |------|-----------|----------| | Docs | "where is X", "explain X" | Docs + suggest code exploration | | Code | "show me code for X" | Full flow through code | | Deep | "explore X thoroughly" | Docs + Code + Related |


Response Format

**Layer:** <c3-id> (<name>)

<Architecture from docs>

**Code References:**
- `path/file.ts` - <role>

**Key Insights:**
<Observations from code>

**Related:** <navigation hints>