bama
BAMA: 모든 Mac 앱을 만들 수 있습니다
CSP는 AI 기반 코딩 기능을 통합한 제품군으로, 핵심 개발 흐름을 하나의 플러그인 가능한 프레임워크로 연결해 생산성을 높입니다
CSP is an integrated suite of AI-driven coding capabilities. It bridges the gap between essential development workflows into a unified, pluggable framework for enhanced productivity.
스킬JavaScript · PythonGitHub @maythyai온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
CSP — Code Skills Package
(./CHANGELOG.md)(./CHANGELOG.md)(./CHANGELOG.md)(./CHANGELOG.md)
Integrates capabilities from multiple open-source AI coding projects into a layered, auto-routing framework with extremely low token costs to complete complex development tasks.
🔗 Live Interactive Dashboard — explore all 664 skills by layer, category, and triggersREADME 전문 보기 ↗Unified AI Programming Skills · 22+ Platforms · 15+ Languages · 685 Skills
Integrates capabilities from multiple open-source AI coding projects into a layered, auto-routing framework with extremely low token costs to complete complex development tasks.
Quick Start · Core Features · Architecture · English
🔗 Live Interactive Dashboard — explore all 685 skills by layer, category, and triggers
CSP (Code Skills Package) consolidates the essence of multiple open-source AI programming projects into an integrated solution. It uses a five-layer architecture to load skills on demand, with confidence scoring router and skill knowledge graph, allowing AI programming assistants to load only the minimum skill set required for each task during a session. At the same time, CSP remembers user usage habits and project context, providing increasingly accurate services as the project evolves. With 684 skills spanning full-stack development, DevOps, security, and a dedicated indie developer toolkit covering deployment, monetization, performance, and more, CSP supports the complete journey from idea to production.
| Feature | CSP Solution | Traditional Solution |
|---|---|---|
| Smart Routing | Confidence scoring + state awareness + knowledge graph, automatically selects optimal skill combinations | Manual plugin selection / full loading |
| Token Savings | Five-layer on-demand loading + index sharding, ~500–1,500 tokens per task | Full loading ~12,000+ tokens |
| Skill Orchestration | Static Recipe + Dynamic DAG, supports branching / parallel / rollback / automatic merging | Fixed pipeline / no orchestration |
| Continuous Learning | 5-dimensional knowledge extraction, gets smarter about projects and developers | Stateless, starts from zero each time |
| Full-Stack Coverage | 684 skills · 5 layers · 15+ languages · 22+ platforms | Single language / limited scenarios |
| Open Extension | Custom Skills + Recipe + Creation Wizard | Closed ecosystem / no extension |
The router is driven by triple state signals, not just keywords:
.csp/state.json): Git status, tech stack, dev phase, test status — auto-detected by the pre-router hook and fed into the context score (phase match +0.2, stack match +0.15, dirty tree biases toward debug skills)..csp/artifacts/*.md): existence of understand/plan/spec/implement/review/verify artifacts determines the current SDD phase and boosts the next skill automatically — so the router knows where you are, not just what you typed..csp/skpg/graph.json, 2,400+ nodes / 5,200+ edges): SKPG dependency checks, impact analysis, and A→B shortest-path finding across 2,200+ trigger keywords.Triple-signal weighted scoring (keywords 40% + intent 30% + context 30%). High confidence routes directly, low confidence uses interactive confirmation, below 50% falls back to deep interview.
Skills self-assemble into workflows via artifact handoff — no manual wiring. When a predecessor's output lands on disk, the successor auto-detects it and skips already-completed phases:
deep-interview spec (.csp/specs/deep-interview-*.md)
→ csp-plan --consensus --direct (reuses spec, skips interview)
→ consensus plan (.csp/plans/consensus-*.md)
→ csp-autopilot (skips Phase 0+1, starts at execution)
The router reports a recommended next skill in its output whenever a handoff artifact is detected.
CSP automates aggressively but never runs away: approval gates pause before decomposition sign-off, tech-stack confirmation, and release; QA stops after the same error repeats 3× (fundamental-issue signal); plan→execution is approval-gated by default. Stop conditions are intentional — they prevent a vague idea from auto-committing all the way to production.
When a gate fails, the engine branches — it doesn't halt:
| Failure | Branch action |
|---|---|
| Decomposition incomplete | retry (max 2×) |
| Tech-design review fails | retry design or review (max 3×) |
| Test failure | insert a debug stage before QA |
| Critical review finding | insert a fix stage before ship |
Four modes (full / lightweight / spec-only / extend) and scope-based escalation/degradation (e.g. csp-simple-dev auto-upgrades to csp-design-hub when scope exceeds 3 files) keep the pipeline matched to task size.
Only L0 router remains resident (~2,000 tokens (SKILL.md + routing index summary)), L1–L4 loads on demand. Index sharding reduces resident tokens by ~85%, dynamic unloading and shared context further reduce long session overhead. Per-task token consumption controlled to ~500–1,500.
Two orchestration modes complement each other: Static Recipe pre-defines skill sequences for common scenarios (feature development, bug fixes, refactoring, quick fixes); Dynamic DAG engine csp-autopilot makes node-by-node decisions, supporting branching parallelism, rollback retries and worktree isolation execution. Complexity classifier automatically matches model tiers.
Automatically extracts knowledge in 5 dimensions at session end — project architecture and tech stack, user requirement patterns, developer coding style and preferences, long-term lessons learned, skill usage feedback. Knowledge persisted to .csp/intel/, reused across sessions, making CSP increasingly accurate as projects evolve.
685 skills distributed across 5 layers, covering the full process of requirement planning, code implementation, review, debugging, testing, and release, extending to specialized areas such as AI Engineering (RAG/LLM/vLLM), DevOps (CI/CD/IaC/K8s), mobile (React Native/cross-platform), security auditing (STRIDE-A/CodeQL/incident response). Additionally, 31 skills are specifically designed for independent developers, covering deployment (Vercel/Railway/VPS), monetization (Stripe/subscriptions/SEO/analytics), performance tuning, API integration (webhooks/OAuth), testing engineering (E2E/visual regression), internationalization, and monorepo management. Each skill follows the SKILL.md v2 specification, with structured fields like phase/domain/role.
A three-spec governance layer (PMS product-spec / CMS code-spec / TMS test-spec) runs alongside the lifecycle as living baselines: each stage reads the relevant spec before producing, and writes back deltas after shipping — keeping PRD, code, and tests mutually traceable without a separate tool.
Users can define custom workflows via .csp/recipes.yaml, create new skills interactively with csp-skill-creator. Installer supports selective deployment by tech stack (--stacks) and layer (--layers), with --minimal mode installing only the core router.
| Scenario | Input Example | Skill Chain |
|---|---|---|
| Feature Development | "Develop user authentication feature" | brainstorming → spec → plan → execute → tdd → review → verify → ship |
| Bug Fix | "There's a bug in this Django project" | debug + django-patterns → fix → tdd → verify |
| Code Review | "Help me do a code review" | code-review + language reviewer → REVIEW.md |
| Requirements Clarification | "I want to build something but not sure" | interview-me → brainstorming → spec |
| Project Onboarding | "I just took over this project" | explore → map-codebase → architecture mapping |
| Quick Prototyping | "Quickly make a demo" | brainstorming → implement → basic-check |
| Security Audit | "Conduct security review" | security-review + framework security skill → audit report |
| Deploy to Production | "Deploy my app to Vercel" | platform-deploy + indie-deploy-ops → live app |
| Add Payments | "Integrate Stripe subscriptions" | payment-integration + subscription-management + webhook-architecture |
| Performance Tuning | "My app is slow" | frontend-performance + backend-performance + db-performance |
| Go International | "Add multi-language support" | i18n-frameworks + locale-management → localized app |
# Auto-detect AI tool and install
./install.sh
# Install for a specific platform (22 supported)
./install.sh --platform claude-code
./install.sh --platform cursor
# Install into any target directory (no need to clone this project here)
./install.sh --platform cursor --target /path/to/your/project
# Remote one-line install (no clone required)
curl -fsSL https://raw.githubusercontent.com/maythyai/code-skills-package/master/install.sh | bash -s -- --platform cursor
# Remote install to a specific target directory
curl -fsSL https://raw.githubusercontent.com/maythyai/code-skills-package/master/install.sh | bash -s -- --platform cursor --target /path/to/your/project
# npm global install
npm install -g code-skills-package
cd /your/project && csp-install --platform cursor
# Global install
./install.sh --platform trae --global
# Uninstall
./install.sh --uninstall
# List detected platforms
./install.sh --list
Complete installation documentation: INSTALL.md · Update Guide: UPDATE.md
Add to your project CLAUDE.md:
Use CSP (Code Skills Package) skills. When given a task, route to the appropriate skill combination via csp-router.
After that, simply give tasks to AI normally, the router will work automatically:
| Input | Result |
|---|---|
"Do a code review" | Loads csp-code-review + language-specific reviewer |
"Plan and implement user auth" | brainstorming → spec → plan → execute → tdd → review → verify → ship |
"There's a bug in this Django project" | Loads csp-debug + csp-django-patterns |
/csp-plan # Planning phase
/csp-debug # Debugging flow
/csp-review # Code review
/csp-test # Testing flow
/csp-ship # Release flow
/csp-spec-phase # Requirements clarification
/csp-execute-phase # Execute plan
/csp-verify # Verify implementation
/csp-search <query> # Search skill index
/csp-update # Check npm for a newer CSP release and install it
/csp-sync-skills --from claude --to cursor --apply # Sync csp-* skills across runtimes
/csp-doctor # Diagnose installation health
/csp-help # Browse command help
Load csp-react-reviewer to review this code
Load csp-plan-phase to plan this feature
CSP uses a five-layer layered architecture. Only the router (L0) loads at session start, remaining layers load on demand.
┌──────────────────────────────────────────────────────────────┐
│ L0 csp-router Session-start resident (~2,000 tokens) │
│ Task classification + confidence scoring + state │
│ awareness + SKPG knowledge graph enhancement │
├──────────────────────────────────────────────────────────────┤
│ L1 csp-meta Methodology (~300 tokens/skill · 26) │
│ Planning · Debugging · TDD · Brainstorming · Scope Guard│
├──────────────────────────────────────────────────────────────┤
│ L2 csp-workflow Project management (~500 tokens/skill │
│ · 201) plan → execute → verify → ship full lifecycle │
├──────────────────────────────────────────────────────────────┤
│ L3 csp-patterns Language/Framework (~200-600 tokens │
│ · 396) 15+ reviewer · Build fix · Patterns · Security │
│ · Indie Dev (deploy/monetization/perf/i18n/monorepo) │
│ · Responsive/Data-analysis/Paper-reader/UI-design │
├──────────────────────────────────────────────────────────────┤
│ L4 csp-runtime Runtime (~300 tokens/skill · 58) │
│ Continuous learning · Autonomous execution · Knowledge │
│ management · Token budget · File-organizer · Parallel │
└──────────────────────────────────────────────────────────────┘
Total: 685 skills
User input → State detection (Git/tech stack/phase)
→ Keywords + Intent + Regex pattern matching
→ Confidence scoring (keyword×0.4 + intent×0.3 + context×0.3)
→ SKPG dependency check
→ Routing decision
| Confidence | Decision |
|---|---|
| > 80% | Directly route to top skill |
| 50–80% | Show top 3, let user confirm |
| < 50% | Fall back to deep interview (/csp-interview-me) |
| Strategy | Effect |
|---|---|
| Index sharding (on-demand loading by node type) | Resident tokens reduced by ~85% |
| Summary caching (~30 tokens/skill per line) | Avoid repeated loading, reduce 15% |
| Dynamic unloading (release L3/L4 content after completion) | Long sessions reduced by 30% |
Shared context (pass via .csp/artifacts/) | Cross-skill calls reduced by 20% |
Detailed architecture design, DAG orchestration engine, skill knowledge graph, skill retrieval strategy, etc., please refer to ARCHITECTURE.md.
CSP supports two complementary orchestration modes: static Recipes (pre-defined sequences) and dynamic DAG (csp-autopilot makes node-by-node decisions).
# New feature development
feature-development:
sequence: [brainstorming → plan → spec → implement → tdd → review → verify → ship]
# Bug fix
bug-fix:
sequence: [debug → implement → tdd(regression) → verify]
# Refactoring
refactor:
sequence: [review(analyze) → plan → implement → tdd(no-regression) → review(verify)]
# Quick fix
quick-fix:
sequence: [implement → verify(quick-check)]
Define reusable workflows by creating .csp/recipes.yaml in the project root:
recipes:
hotfix:
description: "Urgent production fix, minimize changes"
triggers: ["hotfix", "urgent"]
sequence:
- skill: csp-debug
- skill: csp-implement
mode: minimal-change
- skill: csp-verify-phase
mode: regression-only
- skill: csp-ship
auto: true
Recipe priority: user-defined → built-in → router's dynamic composition.
/csp-why # Why was this skill chosen?
/csp-debug-router # Router matching logs
/csp-stats # Usage statistics
CSP supports 22+ AI programming platforms, including Claude Code, Cursor, Trae, Windsurf, Kiro, Codex, Gemini CLI, JetBrains (Junie), Cline, Roo Code, Neovim (avante.nvim), etc. The installation script automatically detects the platform and generates corresponding configuration files (CLAUDE.md / .cursorrules / .windsurfrules / .junie/guidelines.md / .cline/rules / .roo/rules / .avante/rules, etc.).
For contributors and security-conscious installers:
# Full rebuild of all derived data from SKILL.md frontmatter
npm run build:all # registry → metadata → triggers → graph → page
# Validate skills + triggers + registry schema
npm run validate:all
# Full test suite (validate + graph rebuild + 20 invariant assertions)
npm test
# Scaffold a new validate-passing skill
node bin/csp-sdk.mjs init-skill csp-my-skill --layer 3 --phase build
install.sh is split into install.sh + lib/platforms.sh + lib/bootstrap.sh for maintainability.CSP_SHA256=<hash> to verify the downloaded archive (the hash is printed on every install so you can pin it). CSP_BRANCH is whitelisted against ^[A-Za-z0-9._-]+$ to prevent command injection.SKILL.md frontmatter (v2 fields) → all of registry.json / triggers.yaml / skpg/graph.json / skill-metadata.yaml are derived — never hand-edit them.📖 文档组织与定位见 docs/README.md(README 门面 · docs/ 对外人类文档 · .csp/ 对内 agent 产物库三层关系)。
| Document | Description |
|---|---|
| ARCHITECTURE.md | Complete architecture design (14 chapters · DAG orchestration · SKPG · Token strategy) |
| SKILL-INDEX.md | Complete index of 684 skills/agents |
| INSTALL.md | Complete installation guide (22+ platforms) |
| UPDATE.md | How to keep an installed skill package up to date |
| SKILL-AUTHORING.md | Skill authoring best practices |
| SKILL-SPEC.md | SKILL.md specification document |
| VERSIONING.md | Version management policy (X=arch, Y=feature, Z=fix) |
| FEATURES.md | Feature inventory (version × module × feature × integration status) |
| USER-GUIDE.md | User guide |
| examples/ | Five worked examples (code review, security review, build-fix, simplification, dashboard) |
All integrated projects use the MIT license.
CSP integrates capabilities from the following open-source projects:
| Project | Contribution Area |
|---|---|
| ECC | Skill library |
| GSD | Project management & lifecycle workflows |
| OMC | Runtime enhancement (autopilot · wiki · remember) |
| Superpowers | Meta-skills & methodology |
| spec-kit | Spec-driven development |
| Agency-Agents | Specialized AI agents |
| awesome-copilot | GitHub Copilot skills & agents (~40 selected) |
| Build / validation / maintenance tooling reference |
| CONTRIBUTING.md | How to contribute a skill or fix |
| CHANGELOG.md | Release history |
| docs/analysis/ | Audit reports and cross-layer testing case study |
| README_zh.md | Chinese Documentation |