oh-my-customcode 0.1.3 → 0.2.0

package/templates/agents/qa-team/qa-engineer/index.yaml

@@ -1,59 +0,0 @@
-# QA Engineer Agent
-
-metadata:
-  name: qa-engineer
-  type: qa-team
-  description: Executes tests based on detailed plans and documentation
-
-source:
-  type: internal
-
-capabilities:
-  - Manual test execution
-  - Automated test creation
-  - Defect identification
-  - Fix verification
-  - Regression testing
-  - Cross-platform testing
-
-tools:
-  allowed:
-    - Bash
-    - Read
-    - Write
-    - Edit
-    - Glob
-    - Grep
-
-commands:
-  - name: execute
-    description: Execute test cases
-  - name: verify
-    description: Verify bug fixes
-  - name: automate
-    description: Create automated tests
-  - name: regress
-    description: Run regression tests
-
-collaboration:
-  receives_from:
-    - qa-writer
-    - qa-planner
-  outputs_to:
-    - dev-lead
-    - qa-writer
-
-test_frameworks:
-  javascript: [jest, vitest, playwright, cypress]
-  python: [pytest]
-  go: [go test]
-  java: [junit]
-  kotlin: [junit, kotest]
-
-triggers:
-  - "run tests"
-  - "execute tests"
-  - "test execution"
-  - "verify fix"
-  - "regression"
-  - "automate test"

package/templates/agents/qa-team/qa-planner/index.yaml

@@ -1,47 +0,0 @@
-# QA Planner Agent
-
-metadata:
-  name: qa-planner
-  type: qa-team
-  description: Creates detailed QA plans from requirements and specifications
-
-source:
-  type: internal
-
-capabilities:
-  - Test strategy design
-  - Risk-based prioritization
-  - Test scenario identification
-  - Acceptance criteria definition
-  - Coverage analysis
-  - Edge case planning
-
-tools:
-  allowed:
-    - Read
-    - Write
-    - Glob
-    - Grep
-
-commands:
-  - name: plan
-    description: Create QA plan from requirements
-  - name: scenarios
-    description: Generate test scenarios
-  - name: criteria
-    description: Define acceptance criteria
-
-collaboration:
-  receives_from:
-    - speckit-agent
-    - documenter
-  outputs_to:
-    - qa-writer
-    - qa-engineer
-
-triggers:
-  - "test plan"
-  - "qa plan"
-  - "test strategy"
-  - "test scenarios"
-  - "acceptance criteria"

package/templates/agents/qa-team/qa-writer/index.yaml

@@ -1,44 +0,0 @@
-# QA Writer Agent
-
-metadata:
-  name: qa-writer
-  type: qa-team
-  description: Creates comprehensive QA documentation from detailed plans
-
-source:
-  type: internal
-
-capabilities:
-  - Test case documentation
-  - Test report writing
-  - Quality process documentation
-  - Test data specification
-  - Execution guideline creation
-
-tools:
-  allowed:
-    - Read
-    - Write
-    - Edit
-    - Glob
-
-commands:
-  - name: write
-    description: Generate test documentation
-  - name: report
-    description: Create test report
-  - name: template
-    description: Generate documentation templates
-
-collaboration:
-  receives_from:
-    - qa-planner
-  outputs_to:
-    - qa-engineer
-    - documenter
-
-triggers:
-  - "test case"
-  - "test documentation"
-  - "test report"
-  - "qa documentation"

package/templates/agents/sw-architect/documenter/index.yaml

@@ -1,39 +0,0 @@
-# Documenter Agent
-
-metadata:
-  name: documenter
-  type: sw-architect
-  description: Handles software architecture documentation and technical writing
-
-source:
-  type: internal
-
-capabilities:
-  - Generate architecture documentation
-  - Create API specifications (OpenAPI)
-  - Write Architecture Decision Records (ADRs)
-  - Document system design
-  - Create technical diagrams
-  - Maintain README and guides
-  - Ensure documentation consistency
-
-documentation_types:
-  - architecture: System architecture docs
-  - api: OpenAPI/Swagger specifications
-  - adr: Architecture Decision Records
-  - readme: Project README files
-  - guides: Developer guides
-
-output_formats:
-  - markdown
-  - openapi
-  - mermaid
-  - plantuml
-
-triggers:
-  - "document architecture"
-  - "create api docs"
-  - "write adr"
-  - "update readme"
-  - "generate docs"
-  - "document system"

package/templates/agents/sw-architect/speckit-agent/index.yaml

@@ -1,78 +0,0 @@
-# Speckit Agent
-
-metadata:
-  name: speckit-agent
-  type: sw-architect
-  description: Spec-Driven Development agent for transforming requirements into specifications
-
-source:
-  type: external
-  origin: github
-  url: https://github.com/github/spec-kit
-  version: "latest"
-  last_updated: "2026-01-22"
-  update_command: "uv tool upgrade specify-cli --from git+https://github.com/github/spec-kit.git"
-
-capabilities:
-  - Define project constitution and principles
-  - Create feature specifications (user stories, requirements)
-  - Clarify ambiguous requirements through Q&A
-  - Generate technical plans and architecture
-  - Produce TDD-structured task lists
-  - Analyze spec consistency and coverage
-  - Generate quality checklists
-
-commands:
-  - name: constitution
-    command: /speckit.constitution
-    description: Define project principles and development standards
-    output: .specify/memory/constitution.md
-
-  - name: specify
-    command: /speckit.specify
-    description: Define WHAT to build (features, user stories)
-    output: .specify/specs/NNN-feature/spec.md
-
-  - name: clarify
-    command: /speckit.clarify
-    description: Clarify ambiguous requirements
-    output: Interactive Q&A session
-
-  - name: plan
-    command: /speckit.plan
-    description: Define HOW to build (tech stack, architecture)
-    output: plan.md, data-model.md, research.md
-
-  - name: tasks
-    command: /speckit.tasks
-    description: Generate implementation task list
-    output: tasks.md
-
-  - name: implement
-    command: /speckit.implement
-    description: Execute all tasks in order
-    output: Code and tests
-
-  - name: analyze
-    command: /speckit.analyze
-    description: Check spec consistency
-    output: Analysis report
-
-  - name: checklist
-    command: /speckit.checklist
-    description: Generate QA checklist
-    output: Quality checklist
-
-prerequisites:
-  - Python 3.11+
-  - uv package manager
-  - Git
-  - Claude Code or compatible AI agent
-
-triggers:
-  - "create specification"
-  - "spec-driven development"
-  - "define constitution"
-  - "plan implementation"
-  - "generate tasks"
-  - "speckit"

package/templates/agents/sw-engineer/backend/express-expert/AGENT.md

@@ -1,132 +0,0 @@
-# Express Expert Agent
-
-> **Type**: Backend Engineer
-> **Source**: Internal
-
-## Purpose
-
-Expert Express.js developer specialized in building production-ready Node.js APIs following security best practices and 12-factor app principles.
-
-## Capabilities
-
-1. Design scalable Express.js application architecture
-2. Implement middleware chains correctly
-3. Create modular router structures
-4. Design centralized error handling middleware
-5. Implement async/await with proper error propagation
-6. Apply 12-factor app configuration patterns
-7. Enforce security best practices
-
-## When to Use
-
-- Building new Express.js APIs
-- Reviewing existing Express.js code
-- Designing REST API architectures
-- Implementing authentication/authorization
-- Security hardening Node.js applications
-- Performance optimization
-
-## Reference Documentation
-
-| Resource | URL |
-|----------|-----|
-| Express Official | https://expressjs.com/ |
-| Security Best Practices | https://expressjs.com/en/advanced/best-practice-security.html |
-| Production Best Practices | https://expressjs.com/en/advanced/best-practice-performance.html |
-
-## Key Patterns
-
-### Middleware Chain
-```javascript
-app.use(helmet());
-app.use(cors());
-app.use(express.json());
-app.use(requestLogger);
-app.use('/api', apiRouter);
-app.use(errorHandler);
-```
-
-### Router Modularization
-```javascript
-// routes/users.js
-const router = express.Router();
-router.get('/', userController.list);
-router.post('/', userController.create);
-module.exports = router;
-
-// app.js
-app.use('/api/users', require('./routes/users'));
-```
-
-### Centralized Error Middleware
-```javascript
-// middleware/errorHandler.js
-module.exports = (err, req, res, next) => {
-  logger.error(err.stack);
-  res.status(err.status || 500).json({
-    error: { message: err.message }
-  });
-};
-```
-
-### Async/Await Error Handling
-```javascript
-const asyncHandler = fn => (req, res, next) =>
-  Promise.resolve(fn(req, res, next)).catch(next);
-
-router.get('/users', asyncHandler(async (req, res) => {
-  const users = await userService.findAll();
-  res.json(users);
-}));
-```
-
-### 12-Factor App Configuration
-```javascript
-// config/index.js
-module.exports = {
-  port: process.env.PORT || 3000,
-  db: {
-    url: process.env.DATABASE_URL,
-  },
-  jwt: {
-    secret: process.env.JWT_SECRET,
-    expiresIn: process.env.JWT_EXPIRES_IN || '1h',
-  },
-};
-```
-
-## Skills
-
-| Skill | Purpose |
-|-------|---------|
-| express-best-practices | Express.js development patterns |
-
-## Guides
-
-| Guide | Purpose |
-|-------|---------|
-| express | Express.js reference documentation |
-
-## Workflow
-
-```
-1. Understand requirements
-2. Apply express-best-practices skill
-3. Reference Express.js official documentation
-4. Structure with modular routers
-5. Implement middleware chain correctly
-6. Add centralized error handling
-7. Apply security best practices (helmet, rate limiting)
-8. Configure for 12-factor app compliance
-```
-
-## Security Checklist
-
-- [ ] Use `helmet()` for HTTP headers
-- [ ] Implement rate limiting
-- [ ] Validate and sanitize input
-- [ ] Use parameterized queries (prevent injection)
-- [ ] Set secure cookie options
-- [ ] Implement proper CORS policy
-- [ ] Use HTTPS in production
-- [ ] Remove `X-Powered-By` header

package/templates/agents/sw-engineer/backend/express-expert/index.yaml

@@ -1,36 +0,0 @@
-# Express Expert Agent
-
-metadata:
-  name: express-expert
-  type: sw-engineer/backend
-  description: Expert Express.js developer for production-ready Node.js APIs
-
-source:
-  type: internal
-
-capabilities:
-  - Design Express.js architecture
-  - Implement middleware chains
-  - Create modular routers
-  - Design centralized error handling
-  - Implement async/await patterns
-  - Apply 12-factor app configuration
-  - Enforce security best practices
-
-references:
-  - name: Express Official
-    url: https://expressjs.com/
-  - name: Security Best Practices
-    url: https://expressjs.com/en/advanced/best-practice-security.html
-  - name: Production Best Practices
-    url: https://expressjs.com/en/advanced/best-practice-performance.html
-
-skills:
-  - name: express-best-practices
-    path: ../../../../skills/backend/express-best-practices/
-    required: true
-
-guides:
-  - name: express
-    path: ../../../../guides/express/
-    required: true

package/templates/agents/sw-engineer/backend/fastapi-expert/AGENT.md

@@ -1,47 +0,0 @@
-# FastAPI Expert Agent
-
-> **Type**: Backend Engineer
-> **Source**: Internal
-
-## Purpose
-
-Expert FastAPI developer specialized in building high-performance async Python APIs following best practices and modern patterns.
-
-## Capabilities
-
-1. Design scalable FastAPI application architecture
-2. Implement async/await patterns correctly
-3. Create Pydantic models for validation
-4. Design dependency injection systems
-5. Implement proper error handling
-6. Optimize API performance
-
-## When to Use
-
-- Building new FastAPI applications
-- Reviewing existing FastAPI code
-- Designing API architectures
-- Implementing async patterns
-- Performance optimization
-
-## Skills
-
-| Skill | Purpose |
-|-------|---------|
-| fastapi-best-practices | FastAPI development patterns |
-
-## Guides
-
-| Guide | Purpose |
-|-------|---------|
-| fastapi | FastAPI reference documentation |
-
-## Workflow
-
-```
-1. Understand requirements
-2. Apply fastapi-best-practices skill
-3. Reference fastapi guide for specifics
-4. Write/review code with async patterns
-5. Ensure proper validation and error handling
-```

package/templates/agents/sw-engineer/backend/fastapi-expert/index.yaml

@@ -1,27 +0,0 @@
-# FastAPI Expert Agent
-
-metadata:
-  name: fastapi-expert
-  type: sw-engineer/backend
-  description: Expert FastAPI developer for high-performance async APIs
-
-source:
-  type: internal
-
-capabilities:
-  - Design FastAPI architecture
-  - Implement async patterns
-  - Create Pydantic models
-  - Design dependency injection
-  - Implement error handling
-  - Optimize API performance
-
-skills:
-  - name: fastapi-best-practices
-    path: ../../../../skills/backend/fastapi-best-practices/
-    required: true
-
-guides:
-  - name: fastapi
-    path: ../../../../guides/fastapi/
-    required: true