[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-73398":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":9,"language":10,"languages":9,"totalLinesOfCode":9,"stars":11,"forks":12,"watchers":13,"openIssues":14,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":16,"stars7d":17,"stars30d":18,"stars90d":15,"forks30d":15,"starsTrendScore":19,"compositeScore":20,"rankGlobal":9,"rankLanguage":9,"license":21,"archived":22,"fork":22,"defaultBranch":23,"hasWiki":24,"hasPages":22,"topics":25,"createdAt":9,"pushedAt":9,"updatedAt":26,"readmeContent":27,"aiSummary":28,"trendingCount":15,"starSnapshotCount":15,"syncStatus":29,"lastSyncTime":30,"discoverSource":31},73398,"claude-code-infrastructure-showcase","diet103\u002Fclaude-code-infrastructure-showcase","diet103","Examples of my Claude Code infrastructure with skill auto-activation, hooks, and agents",null,"Shell",9697,1220,103,13,0,5,10,64,15,86.66,"MIT License",false,"main",true,[],"2026-06-12 04:01:09","# Claude Code Infrastructure Showcase\n\n**A curated reference library of production-tested Claude Code infrastructure.**\n\nBorn from 6 months of real-world use managing a complex TypeScript microservices project, this showcase provides the patterns and systems that solved the \"skills don't activate automatically\" problem and scaled Claude Code for enterprise development.\n\n> **This is NOT a working application** - it's a reference library. Copy what you need into your own projects.\n\n---\n\n## What's Inside\n\n**Production-tested infrastructure for:**\n- ✅ **Auto-activating skills** via hooks\n- ✅ **Modular skill pattern** (500-line rule with progressive disclosure)\n- ✅ **Specialized agents** for complex tasks\n- ✅ **Dev docs system** that survives context resets\n- ✅ **Comprehensive examples** using generic blog domain\n\n**Time investment to build:** 6 months of iteration\n**Time to integrate into your project:** 15-30 minutes\n\n---\n\n## Quick Start - Pick Your Path\n\n### 🤖 Using Claude Code to Integrate?\n\n**Claude:** Read [`CLAUDE_INTEGRATION_GUIDE.md`](CLAUDE_INTEGRATION_GUIDE.md) for step-by-step integration instructions tailored for AI-assisted setup.\n\n### 🎯 I want skill auto-activation\n\n**The breakthrough feature:** Skills that actually activate when you need them.\n\n**What you need:**\n1. The skill-activation hooks (2 files)\n2. A skill or two relevant to your work\n3. 15 minutes\n\n**👉 [Setup Guide: .claude\u002Fhooks\u002FREADME.md](.claude\u002Fhooks\u002FREADME.md)**\n\n### 📚 I want to add ONE skill\n\nBrowse the [skills catalog](.claude\u002Fskills\u002F) and copy what you need.\n\n**Available:**\n- **backend-dev-guidelines** - Node.js\u002FExpress\u002FTypeScript patterns\n- **frontend-dev-guidelines** - React\u002FTypeScript\u002FMUI v7 patterns\n- **skill-developer** - Meta-skill for creating skills\n- **route-tester** - Test authenticated API routes\n- **error-tracking** - Sentry integration patterns\n\n**👉 [Skills Guide: .claude\u002Fskills\u002FREADME.md](.claude\u002Fskills\u002FREADME.md)**\n\n### 🤖 I want specialized agents\n\n10 production-tested agents for complex tasks:\n- Code architecture review\n- Refactoring assistance\n- Documentation generation\n- Error debugging\n- And more...\n\n**👉 [Agents Guide: .claude\u002Fagents\u002FREADME.md](.claude\u002Fagents\u002FREADME.md)**\n\n---\n\n## What Makes This Different?\n\n### The Auto-Activation Breakthrough\n\n**Problem:** Claude Code skills just sit there. You have to remember to use them.\n\n**Solution:** UserPromptSubmit hook that:\n- Analyzes your prompts\n- Checks file context\n- Automatically suggests relevant skills\n- Works via `skill-rules.json` configuration\n\n**Result:** Skills activate when you need them, not when you remember them.\n\n### Production-Tested Patterns\n\nThese aren't theoretical examples - they're extracted from:\n- ✅ 6 microservices in production\n- ✅ 50,000+ lines of TypeScript\n- ✅ React frontend with complex data grids\n- ✅ Sophisticated workflow engine\n- ✅ 6 months of daily Claude Code use\n\nThe patterns work because they solved real problems.\n\n### Modular Skills (500-Line Rule)\n\nLarge skills hit context limits. The solution:\n\n```\nskill-name\u002F\n  SKILL.md                  # \u003C500 lines, high-level guide\n  resources\u002F\n    topic-1.md              # \u003C500 lines each\n    topic-2.md\n    topic-3.md\n```\n\n**Progressive disclosure:** Claude loads main skill first, loads resources only when needed.\n\n---\n\n## Repository Structure\n\n```\n.claude\u002F\n├── skills\u002F                 # 5 production skills\n│   ├── backend-dev-guidelines\u002F  (12 resource files)\n│   ├── frontend-dev-guidelines\u002F (11 resource files)\n│   ├── skill-developer\u002F         (7 resource files)\n│   ├── route-tester\u002F\n│   ├── error-tracking\u002F\n│   └── skill-rules.json    # Skill activation configuration\n├── hooks\u002F                  # 6 hooks for automation\n│   ├── skill-activation-prompt.*  (ESSENTIAL)\n│   ├── post-tool-use-tracker.sh   (ESSENTIAL)\n│   ├── tsc-check.sh        (optional, needs customization)\n│   └── trigger-build-resolver.sh  (optional)\n├── agents\u002F                 # 10 specialized agents\n│   ├── code-architecture-reviewer.md\n│   ├── refactor-planner.md\n│   ├── frontend-error-fixer.md\n│   └── ... 7 more\n└── commands\u002F               # 3 slash commands\n    ├── dev-docs.md\n    └── ...\n\ndev\u002F\n└── active\u002F                 # Dev docs pattern examples\n    └── public-infrastructure-repo\u002F\n```\n\n---\n\n## Component Catalog\n\n### 🎨 Skills (5)\n\n| Skill | Lines | Purpose | Best For |\n|-------|-------|---------|----------|\n| [**skill-developer**](.claude\u002Fskills\u002Fskill-developer\u002F) | 426 | Creating and managing skills | Meta-development |\n| [**backend-dev-guidelines**](.claude\u002Fskills\u002Fbackend-dev-guidelines\u002F) | 304 | Express\u002FPrisma\u002FSentry patterns | Backend APIs |\n| [**frontend-dev-guidelines**](.claude\u002Fskills\u002Ffrontend-dev-guidelines\u002F) | 398 | React\u002FMUI v7\u002FTypeScript | React frontends |\n| [**route-tester**](.claude\u002Fskills\u002Froute-tester\u002F) | 389 | Testing authenticated routes | API testing |\n| [**error-tracking**](.claude\u002Fskills\u002Ferror-tracking\u002F) | ~250 | Sentry integration | Error monitoring |\n\n**All skills follow the modular pattern** - main file + resource files for progressive disclosure.\n\n**👉 [How to integrate skills →](.claude\u002Fskills\u002FREADME.md)**\n\n### 🪝 Hooks (6)\n\n| Hook | Type | Essential? | Customization |\n|------|------|-----------|---------------|\n| skill-activation-prompt | UserPromptSubmit | ✅ YES | ✅ None needed |\n| post-tool-use-tracker | PostToolUse | ✅ YES | ✅ None needed |\n| tsc-check | Stop | ⚠️ Optional | ⚠️ Heavy - monorepo only |\n| trigger-build-resolver | Stop | ⚠️ Optional | ⚠️ Heavy - monorepo only |\n| error-handling-reminder | Stop | ⚠️ Optional | ⚠️ Moderate |\n| stop-build-check-enhanced | Stop | ⚠️ Optional | ⚠️ Moderate |\n\n**Start with the two essential hooks** - they enable skill auto-activation and work out of the box.\n\n**👉 [Hook setup guide →](.claude\u002Fhooks\u002FREADME.md)**\n\n### 🤖 Agents (10)\n\n**Standalone - just copy and use!**\n\n| Agent | Purpose |\n|-------|---------|\n| code-architecture-reviewer | Review code for architectural consistency |\n| code-refactor-master | Plan and execute refactoring |\n| documentation-architect | Generate comprehensive documentation |\n| frontend-error-fixer | Debug frontend errors |\n| plan-reviewer | Review development plans |\n| refactor-planner | Create refactoring strategies |\n| web-research-specialist | Research technical issues online |\n| auth-route-tester | Test authenticated endpoints |\n| auth-route-debugger | Debug auth issues |\n| auto-error-resolver | Auto-fix TypeScript errors |\n\n**👉 [How agents work →](.claude\u002Fagents\u002FREADME.md)**\n\n### 💬 Slash Commands (3)\n\n| Command | Purpose |\n|---------|---------|\n| \u002Fdev-docs | Create structured dev documentation |\n| \u002Fdev-docs-update | Update docs before context reset |\n| \u002Froute-research-for-testing | Research route patterns for testing |\n\n---\n\n## Key Concepts\n\n### Hooks + skill-rules.json = Auto-Activation\n\n**The system:**\n1. **skill-activation-prompt hook** runs on every user prompt\n2. Checks **skill-rules.json** for trigger patterns\n3. Suggests relevant skills automatically\n4. Skills load only when needed\n\n**This solves the #1 problem** with Claude Code skills: they don't activate on their own.\n\n### Progressive Disclosure (500-Line Rule)\n\n**Problem:** Large skills hit context limits\n\n**Solution:** Modular structure\n- Main SKILL.md \u003C500 lines (overview + navigation)\n- Resource files \u003C500 lines each (deep dives)\n- Claude loads incrementally as needed\n\n**Example:** backend-dev-guidelines has 12 resource files covering routing, controllers, services, repositories, testing, etc.\n\n### Dev Docs Pattern\n\n**Problem:** Context resets lose project context\n\n**Solution:** Three-file structure\n- `[task]-plan.md` - Strategic plan\n- `[task]-context.md` - Key decisions and files\n- `[task]-tasks.md` - Checklist format\n\n**Works with:** `\u002Fdev-docs` slash command to generate these automatically\n\n---\n\n## ⚠️ Important: What Won't Work As-Is\n\n### settings.json\nThe included `settings.json` is an **example only**:\n- Stop hooks reference specific monorepo structure\n- Service names (blog-api, etc.) are examples\n- MCP servers may not exist in your setup\n\n**To use it:**\n1. Extract ONLY UserPromptSubmit and PostToolUse hooks\n2. Customize or skip Stop hooks\n3. Update MCP server list for your setup\n\n### Blog Domain Examples\nSkills use generic blog examples (Post\u002FComment\u002FUser):\n- These are **teaching examples**, not requirements\n- Patterns work for any domain (e-commerce, SaaS, etc.)\n- Adapt the patterns to your business logic\n\n### Hook Directory Structures\nSome hooks expect specific structures:\n- `tsc-check.sh` expects service directories\n- Customize based on YOUR project layout\n\n---\n\n## Integration Workflow\n\n**Recommended approach:**\n\n### Phase 1: Skill Activation (15 min)\n1. Copy skill-activation-prompt hook\n2. Copy post-tool-use-tracker hook\n3. Update settings.json\n4. Install hook dependencies\n\n### Phase 2: Add First Skill (10 min)\n1. Pick ONE relevant skill\n2. Copy skill directory\n3. Create\u002Fupdate skill-rules.json\n4. Customize path patterns\n\n### Phase 3: Test & Iterate (5 min)\n1. Edit a file - skill should activate\n2. Ask a question - skill should be suggested\n3. Add more skills as needed\n\n### Phase 4: Optional Enhancements\n- Add agents you find useful\n- Add slash commands\n- Customize Stop hooks (advanced)\n\n---\n\n## Getting Help\n\n### For Users\n**Issues with integration?**\n1. Check [CLAUDE_INTEGRATION_GUIDE.md](CLAUDE_INTEGRATION_GUIDE.md)\n2. Ask Claude: \"Why isn't [skill] activating?\"\n3. Open an issue with your project structure\n\n### For Claude Code\nWhen helping users integrate:\n1. **Read CLAUDE_INTEGRATION_GUIDE.md FIRST**\n2. Ask about their project structure\n3. Customize, don't blindly copy\n4. Verify after integration\n\n---\n\n## What This Solves\n\n### Before This Infrastructure\n\n❌ Skills don't activate automatically\n❌ Have to remember which skill to use\n❌ Large skills hit context limits\n❌ Context resets lose project knowledge\n❌ No consistency across development\n❌ Manual agent invocation every time\n\n### After This Infrastructure\n\n✅ Skills suggest themselves based on context\n✅ Hooks trigger skills at the right time\n✅ Modular skills stay under context limits\n✅ Dev docs preserve knowledge across resets\n✅ Consistent patterns via guardrails\n✅ Agents streamline complex tasks\n\n---\n\n## Community\n\n**Found this useful?**\n\n- ⭐ Star this repo\n- 🐛 Report issues or suggest improvements\n- 💬 Share your own skills\u002Fhooks\u002Fagents\n- 📝 Contribute examples from your domain\n\n**Background:**\nThis infrastructure was detailed in a post I made to Reddit [\"Claude Code is a Beast – Tips from 6 Months of Hardcore Use\"](https:\u002F\u002Fwww.reddit.com\u002Fr\u002FClaudeAI\u002Fcomments\u002F1oivjvm\u002Fclaude_code_is_a_beast_tips_from_6_months_of\u002F). After hundreds of requests, this showcase was created to help the community implement these patterns.\n\n\n---\n\n## License\n\nMIT License - Use freely in your projects, commercial or personal.\n\n---\n\n## Quick Links\n\n- 📖 [Claude Integration Guide](CLAUDE_INTEGRATION_GUIDE.md) - For AI-assisted setup\n- 🎨 [Skills Documentation](.claude\u002Fskills\u002FREADME.md)\n- 🪝 [Hooks Setup](.claude\u002Fhooks\u002FREADME.md)\n- 🤖 [Agents Guide](.claude\u002Fagents\u002FREADME.md)\n- 📝 [Dev Docs Pattern](dev\u002FREADME.md)\n\n**Start here:** Copy the two essential hooks, add one skill, and see the auto-activation magic happen.\n","该项目是一个经过生产环境验证的Claude Code基础设施示例库，旨在通过技能自动激活、钩子和代理等功能解决复杂TypeScript微服务项目中的实际问题。核心功能包括通过钩子实现技能自动激活、模块化技能模式（遵循500行规则）、针对复杂任务的专业代理以及能够经受上下文重置考验的开发文档系统。适用于需要提高开发效率、特别是在处理大型TypeScript或React项目时的企业级开发场景。该库提供了详细的集成指南和丰富的示例，便于开发者快速上手并根据自身需求定制。",2,"2026-06-11 03:45:21","high_star"]