Custom plugins and skills for Claude Code.

# Add this repo as a marketplace
/plugin marketplace add ooiyeefei/ccc

# Install the deckling plugin (has /deckling command)
/plugin install deckling@ccc

# Install the skills collection (includes excalidraw and streak)
/plugin install ccc-skills@ccc

Generate and refine PowerPoint presentations using Anthropic's Platform Skills API.

/deckling "Quarterly Review - 3 slides"
/deckling "Change title to 'Q4 Results'" --refine quarterly.pptx

See plugins/deckling/README.md for full documentation.

Analyze web app codebases against a battle-tested 10-point MVP launch checklist. Based on "Realistic MVP Launch Checklist (from building 30+ apps)".

/launch-check

The 10-Point Checklist:

1. Stripe Setup (webhooks, trials, failed payments)
2. Mobile-First Design (real device testing)
3. Smooth Onboarding (minimal steps, fast first win)
4. AI & Automation Stability (retries, error handling)
5. Critical Emails (welcome, trial-ending, failed payment)
6. Error Logging (catch bugs before users)
7. User Feedback Loop (simple form or tool)
8. Auth & Roles (secure pages, basic roles)
9. Custom Domain with SSL (no dev URLs)
10. Real Database & Backups (automated backups)

Philosophy: "Don't overbuild. Just make it stable, usable, and something people can trust."

See plugins/mvp-launch/README.md for full documentation.

Generate architecture diagrams from any codebase as .excalidraw files.

After installing ccc-skills, just ask Claude Code:

"Generate an architecture diagram for this project"
"Create an excalidraw diagram of the system"
"Visualize this codebase as an excalidraw file"

Features:

• Analyzes any codebase (Node.js, Python, Java, Go, etc.)
• No prerequisites - works without existing diagrams or Terraform
• Proper 90-degree elbow arrows (not curved)
• Color-coded components by type (database, API, storage, etc.)
• Dynamic IDs and labels based on discovered components

See skills/excalidraw/SKILL.md for full documentation.

Universal challenge tracker with flexible cadence, intelligent insights, and cross-challenge learning detection.

After installing ccc-skills, use these commands for reliable, deterministic triggering:

/streak              # Check in to active challenge
/streak-new          # Create a new challenge (guided)
/streak-list         # List all challenges
/streak-switch NAME  # Switch active challenge
/streak-stats        # View progress and achievements
/streak-insights     # Cross-challenge insights

You can also ask Claude Code naturally - it will invoke the skill when relevant:

"Check in to my challenge"
"Start a new streak"
"Show my stats"

• Universal: Works for any challenge type (learning, habits, building, fitness, creative, custom)
• Flexible Cadence: Daily, weekly, or custom N-day intervals per challenge
• AI-Powered Insights: Auto-detects compound learning and semantic connections
• Achievements: Streak badges and milestone rewards
• Calendar Export: Optional .ics file for calendar reminders
• Zero Config: Works locally with no external dependencies

• 30 Days of Coding
• Read 12 Books This Year
• Morning Meditation Habit
• Daily Sketching Practice

See skills/streak/README.md for quick start guide. See skills/streak/SKILL.md for full documentation.

AI-native product management for startups. Process signals, not features.

After installing ccc-skills, just ask Claude Code:

"Analyze my product"
"Research competitors"
"Find feature gaps we should build"
"What should we build next?"

/pm analyze     # Deep product understanding
/pm landscape   # Market overview + competitors
/pm gaps        # Batch gap analysis with WINNING scores
/pm file        # Create GitHub Issues for top priorities
/pm roadmap     # Organize into Now/Next/Later

Prioritize with objective scoring: WINNING = Pain × Timing × Execution

• 40-60: FILE (high conviction)
• 25-39: WAIT (monitor)
• 0-24: SKIP (not worth it)

This skill handles WHAT to build (product discovery). For HOW to build, use spec-kit:

/pm file → GitHub Issue → /speckit.specify → /speckit.plan → /speckit.implement

The GitHub Issue IS the handoff—no extra command needed.

See plugins/product-management/README.md for full documentation.

We welcome contributions! CCC follows a hybrid contribution model:

Quick start:

1. Fork the repo
2. Create a branch
3. Make changes and test with Claude Code
4. Submit a PR

See CONTRIBUTING.md for detailed guidelines.

Look for issues labeled good first issue - they're great for getting started!

If you find CCC useful, consider supporting its development:

MIT