Skip to content
Design
Command

/naksha-status

Show current Naksha project memory — brand settings, framework, token format, and recent design decisions.

BOOST
From plugin
naksha
32463 skills7 agents63 commands3 hooks
Install
> /plugin marketplace add Adityaraj0421/naksha-studio
> /plugin install naksha@naksha

How it fires

How this command gets triggered: by you, by Claude, or both.

  • Fires itselfClaude auto-loads it when your prompt matches the work.
  • You can call itInvoke it directly when you want it.
  • Slash command/naksha-status

Context preview

What this command does when you run it.

Show current Naksha project memory — brand settings, framework, token format, and recent design decisions.

Command definition

naksha-status.md
description: "Show current Naksha project memory — brand settings, framework, token format, and recent design decisions."
argument-hint: ""
allowed-tools: ["Read", "Bash"]

/naksha-status

Display the current Naksha project context and memory stored in `.naksha/project.json` and `.naksha/memory.md`.

Process

Step 1: Walk Up Directory Tree

Search for `.naksha/project.json` starting from `$PWD` and walking up to 3 parent directory levels:

for i in 0 1 2 3; do
  path=$(printf '%s' "$PWD" | sed "s|/[^/]*$||;t" | head -c $((${#PWD} - i * (${#PWD} / 4))) || echo "$PWD")
  [ -f "$path/.naksha/project.json" ] && echo "$path/.naksha/project.json" && break
done

Or use a simpler bash loop:

current="$PWD"
found=""
for i in {0..3}; do
  if [ -f "$current/.naksha/project.json" ]; then
    found="$current/.naksha/project.json"
    break
  fi
  parent=$(dirname "$current")
  [ "$parent" = "$current" ] && break
  current="$parent"
done
echo "$found"

Step 2: Check for Project File

If `.naksha/project.json` is **not found**:

No project memory found. Run /naksha-init to set up your project context.

Exit cleanly.

If **found**: proceed to Step 3.

Step 3: Read and Parse project.json

Read the `.naksha/project.json` file. Extract:

**v4 fields:**

  • `name` → project name
  • `brand.primary` → primary color (hex)
  • `brand.secondary` → secondary color (hex, may be absent)
  • `brand.font` → font family
  • `brand.voice` → brand voice/tone description
  • `framework` → framework name
  • `tokenFormat` → token format name
  • `createdAt` → ISO timestamp
  • `designSystemPath` → design system path (may be absent)

**v5 fields (if present — all optional):**

  • `schema_version` → `"5"` if v5; absent if v4
  • `constraints` → full constraints object
  • `component_patterns` → array of recorded UI patterns
  • `browser_findings` → array of browser research captures

**v5.3 fields (if present — optional):**

  • `taste.signals` → approved/rejected design directions recorded by `/naksha-taste` and `/design-variants`. Weight each by age (≤ 90 days = 1, 91–180 days = 0.5, older = 0) and sum per trait.

Step 4: Generate Color Hints

For each color (primary and secondary), append a human-readable color name hint:

#6366F1 → indigo
#F59E0B → amber
#10B981 → emerald
#3B82F6 → blue
#EF4444 → red
#8B5CF6 → purple
#EC4899 → pink
#F97316 → orange
#FBBF24 → yellow
#6366F1 → indigo
#14B8A6 → teal
#000000 → black
#FFFFFF → white
#808080 → gray

Use a basic color matching: convert the hex to HSL or RGB and find the closest standard web color name. If no close match, just display the hex value without a hint.

Step 5: Read memory.md (if exists)

Check if `.naksha/memory.md` exists (same directory as project.json):

memory_file="$(dirname "$project_json")/memory.md"
[ -f "$memory_file" ] && cat "$memory_file"

Extract the last 10 entries (lines that start with `[`) from memory.md, with newest first (reverse order).

Format of memory entries: `[YYYY-MM-DDTHH:MM:SSZ] /command: description`

Step 6: Build Output

Render a formatted status dashboard:

## Naksha Project Status

**Project:** {name}   **Schema:** {v5 if schema_version is "5", else v4}
**Initialized:** {createdAt date in YYYY-MM-DD format}

### Brand
| Setting | Value |
|---------|-------|
| Primary color | {primary} ({color hint}) |
| Secondary color | {secondary} ({color hint}) or "—" if absent |
| Font | {font} |
| Voice | {voice} |

### Technical
| Setting | Value |
|---------|-------|
| Framework | {framework} |
| Token format | {tokenFormat} |
| Design system path | {designSystemPath} or "—" if absent |

{If constraints object is present AND has at least one field:}
### Constraints
| Constraint | Value |
|------------|-------|
| Grid | {constraints.grid} or — |
| Dark mode | {constraints.dark_mode — "disabled" / "required" / "—"} |
| Min contrast ratio | {constraints.min_contrast_ratio} or — |
| Breakpoints | {constraints.breakpoints joined as "768 / 1024 / 1280"} or — |
| Max content width | {constraints.max_content_width}px or — |
| Accessibility target | {constraints.accessibility_target} or — |
| Out of scope | {constraints.out_of_scope joined as bullet list} or — |
| Notes | {constraints.notes joined as bullet list} or — |

{If component_patterns array is present AND non-empty:}
### Component Patterns ({count})
{For each pattern:}
- **{name}** — {description}

{If browser_findings array is present AND non-empty:}
### Browser Research ({count} captures)
{For each finding, most recent first, max 5:}
- [{mode}] {url} — {patterns.length} patterns  ({captured_at as YYYY-MM-DD})

{If taste.signals is present AND non-empty:}
### Taste ({count} signals, {active} active)
- Leans toward: {top 3 approved traits by weight} or —
- Steers away from: {top 3 rejected traits by weight} or —
{If any trait appears in both approved and rejected signals:}
- Conflicted: {trait} — newer verdict {approved|rejected}

### Recent Decisions (last 10)
{numbered list of last 10 memory entries, with newest first}

---
Run `/naksha-init` to update brand/framework settings.
Run `/naksha-remember <decision>` to add constraints or component patterns.
Run `/naksha-browse <url>` to capture design research.
Run `/naksha-taste` to see or record your taste, or `/design-variants <task>` to compare directions.

Example Output

## Naksha Project Status

**Project:** Lumina SaaS   **Schema:** v5
**Initialized:** 2026-03-17

### Brand
| Setting | Value |
|---------|-------|
| Primary color | #6366F1 (indigo) |
| Secondary color | #F59E0B (amber) |
| Font | Inter |
| Voice | professional and approachable |

### Technical
| Setting | Value |
|---------|-------|
| Framework | nextjs |
| Token format | css-vars |
| Design system path | src/tokens/tokens.css |

### Constraints
| Constraint | Value |
|------------|-------|
| Grid | 8px |
| Dark mode | disabled |
| Accessibility target | WCAG AA |
| Out of scope | RTL support · p
Read more
Ships withnaksha

Your agency's design brain. Always on, always yours. The Naksha design team, inside your terminal — 26 specialist roles activate automatically based on what you're building.

Get the whole plugin

Other commands on naksha.

ab-variants
Command

ab-variants

Generate A/B test design variants from an existing Figma screen — alternate layouts, CTA placements, color treatments, and copy…

brand-kit
Command

brand-kit

Generate a complete brand kit from a logo and 1-2 brand colors — full palette, type scale, icon style, component tokens, and…