Skip to content

Add domain-discovery and tree-generator meta-skills (v2.1)#4

Merged
LadyBluenotes merged 2 commits into
mainfrom
add-meta-skills
Feb 25, 2026
Merged

Add domain-discovery and tree-generator meta-skills (v2.1)#4
LadyBluenotes merged 2 commits into
mainfrom
add-meta-skills

Conversation

@KyleAMathews

Copy link
Copy Markdown
Collaborator

Summary

  • Adds skills/domain-discovery/SKILL.md (v2.1) — interviews library maintainers to produce a structured domain map (domain_map.yaml + skill_spec.md)
  • Adds skills/tree-generator/SKILL.md (v2.1) — generates SKILL.md files from a domain map

Both skills incorporate feedback from testing against TanStack DB (discussions #2 and #3).

Key changes from v2.0 feedback

domain-discovery:

  • Cross-domain failure modes with domains list — semi-lattice coverage so the same advice appears in every relevant SKILL file
  • Tensions section for explicit cross-domain design conflicts
  • AI-agent-specific failure mode questions (Phase 3c) — produced the most critical findings in testing
  • Subsystem and reference candidate flagging so the tree-generator knows where depth is needed
  • Composition discovery from package.json peer deps before interview
  • Failure mode status field (active / fixed-but-legacy-risk / removed)

tree-generator:

  • Source repository layout for npm distribution in monorepos + package.json files array guidance
  • Framework-integration domain decomposition per adapter package
  • Writes cross-domain failure modes into all relevant SKILL files
  • Tension notes with cross-references between involved domain skills
  • Content-based reference file heuristics (adapter-heavy domains, dense API surfaces, schema validation) — not just 500-line overflow

Test plan

🤖 Generated with Claude Code

KyleAMathews and others added 2 commits February 25, 2026 08:59
Incorporates feedback from TanStack DB testing (discussions #2 and #3):

domain-discovery:
- Cross-domain failure modes with `domains` list for semi-lattice coverage
- Tensions section for design conflicts between domains
- AI-agent-specific failure mode interview questions (Phase 3c)
- Composition discovery from package.json peer deps (Phase 2h)
- Subsystem and reference candidate flagging per domain (Phase 2c)
- Relaxed interview batching for yes/no confirmations
- Failure mode status tracking (active/fixed-but-legacy-risk/removed)
- Strengthened GitHub issue scanning for architectural positions

tree-generator:
- Source repository layout for npm distribution in monorepos
- package.json `files` array guidance for shipping skills
- Framework-integration domain decomposition per adapter package
- Adapter-heavy domain guidance (per-adapter reference files)
- Cross-domain failure modes written into all relevant SKILL files
- Tension notes with cross-references between involved skills
- Failure mode status handling (skip removed, annotate legacy-risk)
- Content-based reference file heuristics (not just length overflow)
- Dense API surface and schema validation reference file triggers

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
- Remove phantom package_map.yaml references from tree-generator
- Fix Phase 3f → 3e cross-reference in domain-discovery
- Fix metadata.sources → sources in validation table
- Add failure mode → Common Mistake mapping note
- Clarify cross-domain failure mode canonical location (list once, tag with domains)
- Add skill_spec.md structural template
- Compress plausible/silent/grounded definition in tree-generator
- Add quality warning to compressed domain-discovery fallback
- Clarify "no concept explanations" means external concepts only
- Add composition skill cross-reference to domain-discovery Phase 2h

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@LadyBluenotes LadyBluenotes merged commit bbf1d31 into main Feb 25, 2026
0 of 4 checks passed
@LadyBluenotes LadyBluenotes deleted the add-meta-skills branch February 25, 2026 18:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants