Files
ISA-Frontend/CLAUDE.md
Lorenz Hilpert c7fc8d8661 🚚 refactor(skills): rename tailwind-isa skill to tailwind
- Rename skill directory from tailwind-isa to tailwind
- Update skill name in frontmatter metadata
- Update all references in CLAUDE.md (2 locations)

Simplifies naming while maintaining clear purpose. The skill provides
Tailwind CSS utilities and design system guidance for the ISA project.
2025-10-29 13:37:56 +01:00

4.6 KiB

CLAUDE.md

This file contains meta-instructions for how Claude should work with the ISA-Frontend codebase.

🔴 CRITICAL: Mandatory Agent Usage

You MUST use these subagents for ALL research and knowledge management tasks:

  • docs-researcher: For ALL documentation (packages, libraries, READMEs)
  • docs-researcher-advanced: Auto-escalate when docs-researcher fails
  • Explore: For ALL code pattern searches and multi-file analysis
  • context-manager: For complex projects and knowledge preservation with persistent memory
  • Direct tools (Read/Bash): ONLY for single specific files or commands

NEW: The context-manager now autonomously stores project knowledge (decisions, patterns, solutions) in persistent memory for cross-session learning.

Violations of this rule degrade performance and context quality. NO EXCEPTIONS.

Communication Guidelines

Keep answers concise and focused:

  • Provide direct, actionable responses without unnecessary elaboration
  • Skip verbose explanations unless specifically requested
  • Focus on what the user needs to know, not everything you know
  • Use bullet points and structured formatting for clarity
  • Only provide detailed explanations when complexity requires it

Researching and Investigating the Codebase

🔴 MANDATORY: You MUST use subagents for research. Direct file reading/searching is FORBIDDEN except for single specific files.

Required Agent Usage

Task Type Required Agent Escalation Path
Package/Library Documentation docs-researcher docs-researcher-advanced if not found
Internal Library READMEs docs-researcher Keep context clean
Code Pattern Search Explore Set thoroughness level
Implementation Analysis Explore Multiple file analysis
Single Specific File Read tool directly No agent needed

Documentation Research System (Two-Tier)

  1. ALWAYS start with docs-researcher (Haiku, 30-120s) for any documentation need
  2. Auto-escalate to docs-researcher-advanced (Sonnet, 2-7min) when:
    • Documentation not found
    • Conflicting sources
    • Need code inference
    • Complex architectural questions

Enforcement Examples

❌ WRONG: Read libs/ui/buttons/README.md
✅ RIGHT: Task → docs-researcher → "Find documentation for @isa/ui/buttons"

❌ WRONG: Grep for "signalStore" patterns
✅ RIGHT: Task → Explore → "Find all signalStore implementations"

❌ WRONG: WebSearch for Zod documentation
✅ RIGHT: Task → docs-researcher → "Find Zod validation documentation"

Remember: Using subagents is NOT optional - it's mandatory for maintaining context efficiency and search quality.

Project Knowledge Management with Context-Manager

NEW CAPABILITY: The context-manager subagent has persistent memory that autonomously stores and retrieves project knowledge across sessions.

What Gets Stored Automatically

  • Assigned Tasks: User-assigned tasks with context ("Remember to look up X because of Y"), TODO items, status tracking
  • Architectural Decisions: State management patterns, API integration approaches, component architecture choices
  • Reusable Patterns: Code conventions, testing patterns, error handling approaches
  • Integration Points: API contracts, data flows, module boundaries
  • Domain Knowledge: Business workflows, business rules, user roles/permissions
  • Technical Solutions: Bug fixes with root causes, performance optimizations

When to Use Context-Manager

Use the context-manager subagent PROACTIVELY for:

  • Task Management: Assigning tasks for later ("Remember to investigate X because of Y")
  • Session Continuity: Starting a new session (it will remind you of pending tasks)
  • Complex, multi-step projects requiring coordination
  • Long-running tasks that span multiple sessions
  • Preserving architectural context
  • Learning about resolved issues and their solutions

How It Works

  1. Task Capture: Listens for "Remember to...", "TODO:", "Don't forget...", stores them with full context
  2. Automatic Storage: Proactively stores important discoveries in persistent memory
  3. Knowledge Retrieval: Queries stored knowledge before starting new work
  4. Task Reminders: Proactively reminds you of pending/incomplete tasks at session start
  5. Cross-Session Persistence: Information persists across Claude Code sessions

Benefits: Eliminates context loss, maintains project knowledge, provides task continuity across sessions.