cokit-cli 1.0.8 → 1.2.0

package/templates/repo/.github/skills/ck-ai-artist/references/reasoning-techniques.md

@@ -1,201 +0,0 @@
-# Reasoning Techniques Deep Dive
-
-## Chain of Thought (CoT) Variants
-
-### Zero-Shot CoT
-```
-[Task description]
-
-Think step by step before answering.
-```
-**Use when**: Quick reasoning, no examples available
-**Effectiveness**: +40-60% on reasoning tasks
-
-### Few-Shot CoT
-```
-Example 1:
-Q: [Question]
-A: Let me think through this...
-   Step 1: [Reasoning]
-   Step 2: [Reasoning]
-   Therefore: [Answer]
-
-Example 2:
-Q: [Question]
-A: Breaking this down...
-   First: [Reasoning]
-   Next: [Reasoning]
-   So: [Answer]
-
-Now solve:
-Q: [Your question]
-```
-**Use when**: Complex reasoning, pattern demonstration needed
-**Effectiveness**: +50-80% on complex tasks
-
-### Auto-CoT
-```
-Let me approach this systematically:
-1. Identify the key elements
-2. Analyze relationships
-3. Apply relevant principles
-4. Draw conclusions
-5. Verify my reasoning
-```
-**Use when**: General problem-solving, exploratory reasoning
-
-## Tree of Thoughts (ToT)
-
-### Implementation Pattern
-```
-Problem: [Complex problem]
-
-Generate 3 different approaches:
-
-Approach A:
-- Method: [Description]
-- Reasoning: [Why this might work]
-- Potential issues: [Risks]
-- Confidence: [1-10]
-
-Approach B:
-- Method: [Description]
-- Reasoning: [Why this might work]
-- Potential issues: [Risks]
-- Confidence: [1-10]
-
-Approach C:
-- Method: [Description]
-- Reasoning: [Why this might work]
-- Potential issues: [Risks]
-- Confidence: [1-10]
-
-Evaluate branches:
-- Which has highest success probability?
-- Which has fewest risks?
-- Which is most feasible?
-
-Selected approach: [Best option with justification]
-Execution: [Step-by-step implementation]
-```
-
-**Use when**: Strategic decisions, multiple valid paths, high-stakes problems
-
-## Self-Consistency
-
-### Process
-1. Generate 5 responses at temp=0.7
-2. Extract final answers from each
-3. Take majority vote
-4. Report confidence = agreement %
-
-### Implementation
-```
-Run this prompt 5 times (or use n=5 parameter):
-[Your reasoning task]
-Think step by step and provide final answer.
-
-Aggregate: If 4/5 agree = high confidence
-          If 3/5 agree = medium confidence
-          If split = low confidence, needs review
-```
-
-**Use when**: Math, logic, factual questions with verifiable answers
-
-## ReAct (Reasoning + Acting)
-
-### Full Pattern
-```
-Task: [Goal to achieve]
-
-Thought 1: I need to understand the current situation.
-Action 1: [Observation or tool use]
-Observation 1: [Result from action]
-
-Thought 2: Based on this, I should [next logical step].
-Action 2: [Next action]
-Observation 2: [Result]
-
-Thought 3: Now I can see that [insight].
-Action 3: [Verification or next step]
-Observation 3: [Result]
-
-Thought 4: I have enough information to conclude.
-Final Answer: [Conclusion with reasoning]
-```
-
-**Use when**: Tool-augmented reasoning, research tasks, multi-step analysis
-
-## Least-to-Most Prompting
-
-### Structure
-```
-Complex problem: [Full problem statement]
-
-Step 1: Decomposition
-Break this into simpler subproblems, ordered from easiest to hardest:
-1. [Simplest subproblem]
-2. [Next subproblem, may depend on 1]
-3. [Harder subproblem, may depend on 1,2]
-4. [Final subproblem requiring all above]
-
-Step 2: Sequential Solution
-Subproblem 1: [Solution]
-Using result from 1, Subproblem 2: [Solution]
-Using results from 1,2, Subproblem 3: [Solution]
-Using all results, Subproblem 4: [Solution]
-
-Final integrated answer: [Complete solution]
-```
-
-**Use when**: Mathematical word problems, multi-step procedures, compositional tasks
-
-## Decomposed Prompting (DECOMP)
-
-### Pattern
-```
-Task: [Complex task]
-
-Required capabilities:
-- [Capability 1]: Use [specialized prompt/tool]
-- [Capability 2]: Use [specialized prompt/tool]
-- [Capability 3]: Use [specialized prompt/tool]
-
-Orchestration:
-1. Call [Capability 1] with [input] → get [output1]
-2. Call [Capability 2] with [output1] → get [output2]
-3. Call [Capability 3] with [output2] → get [final output]
-
-Integrate results: [Final response]
-```
-
-**Use when**: Tasks requiring diverse expertise, specialized sub-tasks
-
-## Constitutional AI Reasoning
-
-### Self-Critique Pattern
-```
-Initial response: [Generated content]
-
-Critique against principles:
-- Is it helpful? [Yes/No + reasoning]
-- Is it harmless? [Yes/No + reasoning]
-- Is it honest? [Yes/No + reasoning]
-
-If any No:
-Revised response that addresses [specific issues]:
-[Improved content]
-```
-
-## Choosing the Right Technique
-
-| Task Type | Best Technique |
-|-----------|---------------|
-| Simple reasoning | Zero-shot CoT |
-| Complex multi-step | Few-shot CoT |
-| Strategic decisions | Tree of Thoughts |
-| Factual verification | Self-Consistency |
-| Tool-using tasks | ReAct |
-| Word problems | Least-to-Most |
-| Specialized sub-tasks | DECOMP |
-| Safety-critical | Constitutional AI |

package/templates/repo/.github/skills/ck-backend-development/SKILL.md

@@ -1,93 +0,0 @@
----
-name: 'ck-backend-development'
-description: 'Build robust backend systems with modern technologies (Node.js, Python, Go, Rust), frameworks (NestJS, FastAPI, Django), databases (PostgreSQL, MongoDB, Redis), APIs (REST, GraphQL, gRPC), authentication (OAuth 2.1, JWT), testing strategies, security best practices (OWASP Top 10), performance optimization, scalability patterns (microservices, caching, sharding), DevOps practices (Docker, Kubernetes, CI/CD), and monitoring. Use when designing APIs, implementing authentication, optimizing database queries, setting up CI/CD pipelines, handling security vulnerabilities, building microservices, or developing production-ready backend systems.'
----
-
-# Backend Development Skill
-
-Production-ready backend development with modern technologies, best practices, and proven patterns.
-
-## When to Use
-
-- Designing RESTful, GraphQL, or gRPC APIs
-- Building authentication/authorization systems
-- Optimizing database queries and schemas
-- Implementing caching and performance optimization
-- OWASP Top 10 security mitigation
-- Designing scalable microservices
-- Testing strategies (unit, integration, E2E)
-- CI/CD pipelines and deployment
-- Monitoring and debugging production systems
-
-## Technology Selection Guide
-
-**Languages:** Node.js/TypeScript (full-stack), Python (data/ML), Go (concurrency), Rust (performance)
-**Frameworks:** NestJS, FastAPI, Django, Express, Gin
-**Databases:** PostgreSQL (ACID), MongoDB (flexible schema), Redis (caching)
-**APIs:** REST (simple), GraphQL (flexible), gRPC (performance)
-
-See: `references/backend-technologies.md` for detailed comparisons
-
-## Reference Navigation
-
-**Core Technologies:**
-- `backend-technologies.md` - Languages, frameworks, databases, message queues, ORMs
-- `backend-api-design.md` - REST, GraphQL, gRPC patterns and best practices
-
-**Security & Authentication:**
-- `backend-security.md` - OWASP Top 10 2025, security best practices, input validation
-- `backend-authentication.md` - OAuth 2.1, JWT, RBAC, MFA, session management
-
-**Performance & Architecture:**
-- `backend-performance.md` - Caching, query optimization, load balancing, scaling
-- `backend-architecture.md` - Microservices, event-driven, CQRS, saga patterns
-
-**Quality & Operations:**
-- `backend-testing.md` - Testing strategies, frameworks, tools, CI/CD testing
-- `backend-code-quality.md` - SOLID principles, design patterns, clean code
-- `backend-devops.md` - Docker, Kubernetes, deployment strategies, monitoring
-- `backend-debugging.md` - Debugging strategies, profiling, logging, production debugging
-- `backend-mindset.md` - Problem-solving, architectural thinking, collaboration
-
-## Key Best Practices (2025)
-
-**Security:** Argon2id passwords, parameterized queries (98% SQL injection reduction), OAuth 2.1 + PKCE, rate limiting, security headers
-
-**Performance:** Redis caching (90% DB load reduction), database indexing (30% I/O reduction), CDN (50%+ latency cut), connection pooling
-
-**Testing:** 70-20-10 pyramid (unit-integration-E2E), Vitest 50% faster than Jest, contract testing for microservices, 83% migrations fail without tests
-
-**DevOps:** Blue-green/canary deployments, feature flags (90% fewer failures), Kubernetes 84% adoption, Prometheus/Grafana monitoring, OpenTelemetry tracing
-
-## Quick Decision Matrix
-
-| Need | Choose |
-|------|--------|
-| Fast development | Node.js + NestJS |
-| Data/ML integration | Python + FastAPI |
-| High concurrency | Go + Gin |
-| Max performance | Rust + Axum |
-| ACID transactions | PostgreSQL |
-| Flexible schema | MongoDB |
-| Caching | Redis |
-| Internal services | gRPC |
-| Public APIs | GraphQL/REST |
-| Real-time events | Kafka |
-
-## Implementation Checklist
-
-**API:** Choose style → Design schema → Validate input → Add auth → Rate limiting → Documentation → Error handling
-
-**Database:** Choose DB → Design schema → Create indexes → Connection pooling → Migration strategy → Backup/restore → Test performance
-
-**Security:** OWASP Top 10 → Parameterized queries → OAuth 2.1 + JWT → Security headers → Rate limiting → Input validation → Argon2id passwords
-
-**Testing:** Unit 70% → Integration 20% → E2E 10% → Load tests → Migration tests → Contract tests (microservices)
-
-**Deployment:** Docker → CI/CD → Blue-green/canary → Feature flags → Monitoring → Logging → Health checks
-
-## Resources
-
-- OWASP Top 10: https://owasp.org/www-project-top-ten/
-- OAuth 2.1: https://oauth.net/2.1/
-- OpenTelemetry: https://opentelemetry.io/