DorianandClaude Opus 4.6
cb22131909
- Add [[app_ext:...]] tag format and rewrite extractApps() for reliable app extraction - Wire AppsGrid and RecipeGrid into ContentGridView (was missing on wide desktop) - Add mock Archy node data for standalone dev testing (VITE_MOCK_ARCHY=true) - Fix PromptPalette: z-50 + opaque bg so slash menu renders above chat content - Fix detail banner not updating: add :key to all detail components in ContentPanel - Guide page moved to /guide, chat is now root route, guide auto-selected on first load - Code browser: click opens file in viewer, separate checkbox for chat context selection - Restore folder context selector (round checkbox on hover) in FileTreeNode - Demo projects for prod deployment instead of hardcoded personal paths - Improve Archy context injection with media breakdown and better error logging - Add 11 Claude Code skills for efficient development workflows Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
1.8 KiB
name, description, allowed-tools
| name | description | allowed-tools |
|---|---|---|
| audit-prompts | Deep audit of AI system prompts — find gaps, test extraction coverage, verify tag formats | Bash(*), Read, Glob, Grep, Agent |
Perform a comprehensive audit of AIUI's AI prompt system. Do NOT make changes — report findings only.
Steps
-
Read the full system prompt: Read
packages/app/src/composables/useAI.tsand reconstruct the complete system prompt including all dynamic sections (persona, Wavlake, memory, web search, Archy context, code context). -
Catalog all tag formats: List every
[[type:...]]and[[type_ext:...]]format defined in the prompt. Cross-reference with regexes incontentExtraction.ts. -
Check for gaps: For each content type in
ContentTab(contentFiltering.ts), verify:- Is there a tag format in the system prompt?
- Is there a matching extraction regex?
- Is there a query classifier?
- Is there a grid + detail component?
- Is the tab wired in ContentPanel.vue and ContentGridView.vue?
-
Test extraction coverage: Read the seed prompts in
src/__tests__/fixtures/seedPrompts.ts. For each seed, verify:- Does the extraction function find the expected number of items?
- Are there edge cases that would break extraction?
-
Analyze prompt quality: Check for:
- Conflicting instructions
- Missing edge case handling (e.g., "what if the AI can't find a match?")
- Overly vague instructions
- Missing content types that should have tag formats
-
Check proxy tools: Read
server/claude-proxy.tsand verify tool definitions match what the prompt claims. -
Report: Create a structured summary with:
- Content type coverage matrix (tag/extraction/grid/detail/prompt)
- Identified gaps and inconsistencies
- Priority recommendations