@neyugn/agent-kits 0.5.0 → 0.5.3

package/kits/coder/skills/plan-writing/SKILL.md

@@ -6,7 +6,16 @@ allowed-tools: Read, Write, Edit
 
 # Plan Writing - Structured Task Decomposition
 
-> **Philosophy:** A good plan is a roadmap that prevents wrong turns. Break down before building up.
+## ⚡ Quick Reference
+
+- **4 phases**: Analysis (no code) → Planning (task file) → [User Approval] → Implementation
+- **Plan format**: task slug `.md` · Each task: Agent · Skills · Priority · Dependencies · INPUT/OUTPUT/VERIFY
+- **Never code during planning**: Plan = thinking only · Implement only after approval
+- **Task assignment**: 1 task = 1 agent · 1 owner · explicit dependency chain
+- **File naming**: `{kebab-case-feature}.md` · e.g., `dark-mode.md`, `auth-system.md`
+
+---
+
 
 ---
 
@@ -73,13 +82,11 @@ Level 4: Subtasks (If task is still too large)
 
 ### Good Task Characteristics
 
-| Characteristic      | Description                                       |
-| ------------------- | ------------------------------------------------- |
-| **Observable**      | Has visible output when complete                  |
-| **Verifiable**      | Clear criteria to confirm done                    |
-| **Independent**     | Minimal dependencies blocking start               |
-| **Sized correctly** | 15 min to 4 hours                                 |
-| **Named clearly**   | Action verb + object (e.g., "Create user schema") |
+- **Observable**: Has visible output when complete
+- **Verifiable**: Clear criteria to confirm done
+- **Independent**: Minimal dependencies blocking start
+- **Sized correctly**: 15 min to 4 hours
+- **Named clearly**: Action verb + object (e.g., "Create user schema")
 
 ---
 
@@ -192,12 +199,10 @@ Before estimating, consider:
 
 ### Common Estimation Mistakes
 
-| ❌ Underestimates           | ✅ Include In Estimate         |
-| --------------------------- | ------------------------------ |
-| "Just wire things together" | Integration complexity         |
-| "Tests are quick"           | Edge cases and debugging tests |
-| "I know this codebase"      | Context switching overhead     |
-| "Simple fix"                | Regression testing             |
+- "Just wire things together": Integration complexity
+- "Tests are quick": Edge cases and debugging tests
+- "I know this codebase": Context switching overhead
+- "Simple fix": Regression testing
 
 ---
 
@@ -249,12 +254,10 @@ A task is DONE when:
 
 ### Writing Good Verification Criteria
 
-| ❌ Vague          | ✅ Specific                                    |
-| ----------------- | ---------------------------------------------- |
-| "Works correctly" | "Returns 200 for valid input, 400 for invalid" |
-| "Tested"          | "Unit tests cover happy path + 3 error cases"  |
-| "Integrated"      | "API called successfully from frontend"        |
-| "Complete"        | "All checklist items verified"                 |
+- "Works correctly": "Returns 200 for valid input, 400 for invalid"
+- "Tested": "Unit tests cover happy path + 3 error cases"
+- "Integrated": "API called successfully from frontend"
+- "Complete": "All checklist items verified"
 
 ---
 
@@ -262,36 +265,30 @@ A task is DONE when:
 
 ### When to Update Plan
 
-| Event               | Update Required                    |
-| ------------------- | ---------------------------------- |
-| Task completed      | Check off, add to progress log     |
-| Blocker discovered  | Add to dependencies, update status |
-| Scope change        | Revise tasks, re-estimate          |
-| New information     | Update risks/decisions log         |
-| End of work session | Mark current progress              |
+- Task completed: Check off, add to progress log
+- Blocker discovered: Add to dependencies, update status
+- Scope change: Revise tasks, re-estimate
+- New information: Update risks/decisions log
+- End of work session: Mark current progress
 
 ### Plan Review Frequency
 
-| Project Duration | Review Frequency           |
-| ---------------- | -------------------------- |
-| < 1 day          | Start and end              |
-| 1-3 days         | Daily                      |
-| > 3 days         | Daily + weekly deep review |
+- < 1 day: Start and end
+- 1-3 days: Daily
+- > 3 days: Daily + weekly deep review
 
 ---
 
 ## 🚨 Anti-Patterns
 
-| ❌ Don't                    | ✅ Do                                |
-| --------------------------- | ------------------------------------ |
-| Giant monolithic tasks      | Break into 15min-4hr chunks          |
-| "It depends on everything"  | Map only true blocking dependencies  |
-| Estimate without buffers    | Apply confidence multiplier          |
-| Skip verification criteria  | Define "done" for every task         |
-| Never update the plan       | Update as you learn                  |
-| Plan at wrong granularity   | Match plan detail to project size    |
-| Plan replaces communication | Plan supplements communication       |
-| Over-plan simple work       | Use judgment on when plans add value |
+- Giant monolithic tasks: Break into 15min-4hr chunks
+- "It depends on everything": Map only true blocking dependencies
+- Estimate without buffers: Apply confidence multiplier
+- Skip verification criteria: Define "done" for every task
+- Never update the plan: Update as you learn
+- Plan at wrong granularity: Match plan detail to project size
+- Plan replaces communication: Plan supplements communication
+- Over-plan simple work: Use judgment on when plans add value
 
 ---
 
@@ -299,17 +296,15 @@ A task is DONE when:
 
 ### Good Task Names
 
-| Format                | Examples                           |
-| --------------------- | ---------------------------------- |
-| `Create [thing]`      | Create user authentication schema  |
-| `Implement [feature]` | Implement password reset flow      |
-| `Update [existing]`   | Update API error handling          |
-| `Add [capability]`    | Add email validation to signup     |
-| `Remove [deprecated]` | Remove legacy auth endpoints       |
-| `Fix [issue]`         | Fix timezone conversion bug        |
-| `Migrate [from → to]` | Migrate users table to new schema  |
-| `Test [component]`    | Test payment processing edge cases |
-| `Document [topic]`    | Document API authentication flow   |
+- `Create [thing]`: Create user authentication schema
+- `Implement [feature]`: Implement password reset flow
+- `Update [existing]`: Update API error handling
+- `Add [capability]`: Add email validation to signup
+- `Remove [deprecated]`: Remove legacy auth endpoints
+- `Fix [issue]`: Fix timezone conversion bug
+- `Migrate [from → to]`: Migrate users table to new schema
+- `Test [component]`: Test payment processing edge cases
+- `Document [topic]`: Document API authentication flow
 
 ---
 
@@ -348,12 +343,10 @@ Before starting implementation:
 
 ## 🔗 Related Skills
 
-| Need                      | Skill                  |
-| ------------------------- | ---------------------- |
-| Discovery before planning | `brainstorming`        |
-| Debugging with structure  | `systematic-debugging` |
-| Clean implementation      | `clean-code`           |
-| API task breakdown        | `api-patterns`         |
+- Discovery before planning: `brainstorming`
+- Debugging with structure: `systematic-debugging`
+- Clean implementation: `clean-code`
+- API task breakdown: `api-patterns`
 
 ---
 

package/kits/coder/skills/postgres-patterns/SKILL.md

@@ -7,20 +7,28 @@ version: 2.0
 
 # PostgreSQL Patterns - Advanced Optimization
 
-> **Philosophy:** PostgreSQL is not just a database—it's a platform. Master its unique features to build performant, secure systems.
+## ⚡ Quick Reference
+
+- **EXPLAIN**: `EXPLAIN ANALYZE` for slow queries · Seq Scan on large tables = add index · `Index Scan` = optimal
+- **Indexes**: B-tree (default) · GIN (JSON/full-text) · BRIN (time-series) · Composite: leftmost column rule
+- **RLS**: `ALTER TABLE t ENABLE ROW LEVEL SECURITY` · Policy per tenant via `current_setting('app.tenant_id')`
+- **Transactions**: Use explicit `BEGIN/COMMIT` for multi-statement · `FOR UPDATE` for pessimistic locking
+- **JSON**: `jsonb` not `json` · Index with GIN · `->` for key · `->>` for text value
+- **Performance**: Connection pooling (PgBouncer) · `VACUUM ANALYZE` periodically · Partial indexes for filtered queries
+
+---
+
 
 ---
 
 ## When to Use This Skill
 
-| ✅ Use                          | ❌ Don't Use                 |
-| ------------------------------- | ---------------------------- |
-| PostgreSQL schema design        | Database-agnostic design     |
-| Query optimization with EXPLAIN | Choosing between databases   |
-| Row-Level Security (RLS)        | ORM selection                |
-| Partitioning strategies         | Non-PostgreSQL databases     |
-| PostgreSQL-specific data types  | Basic normalization concepts |
-| JSONB, arrays, range types      | N+1 query patterns (use ORM) |
+- PostgreSQL schema design: Database-agnostic design
+- Query optimization with EXPLAIN: Choosing between databases
+- Row-Level Security (RLS): ORM selection
+- Partitioning strategies: Non-PostgreSQL databases
+- PostgreSQL-specific data types: Basic normalization concepts
+- JSONB, arrays, range types: N+1 query patterns (use ORM)
 
 ➡️ For general database concepts, see `database-design` skill.
 
@@ -157,14 +165,12 @@ SELECT * FROM orders WHERE user_id = 123;
 
 ### Common Optimizations
 
-| Problem                  | Solution                             |
-| ------------------------ | ------------------------------------ |
-| Seq Scan on filtered col | Add index on WHERE columns           |
-| Slow ORDER BY            | Index matches ORDER BY columns       |
-| Low selectivity          | Partial index on common filter       |
-| JSONB field queries      | Extract to generated column + B-tree |
-| LIKE '%pattern%'         | pg_trgm extension + GIN index        |
-| Cross-table queries      | Covering index with INCLUDE          |
+- Seq Scan on filtered col: Add index on WHERE columns
+- Slow ORDER BY: Index matches ORDER BY columns
+- Low selectivity: Partial index on common filter
+- JSONB field queries: Extract to generated column + B-tree
+- LIKE '%pattern%': pg_trgm extension + GIN index
+- Cross-table queries: Covering index with INCLUDE
 
 ### Join Optimization
 
@@ -206,12 +212,10 @@ ALTER TABLE documents FORCE ROW LEVEL SECURITY;
 
 ### When to Partition
 
-| Criteria       | Threshold        |
-| -------------- | ---------------- |
-| Table size     | > 100M rows      |
-| Query filter   | Always on date   |
-| Data lifecycle | Retention policy |
-| Maintenance    | Bulk deletes     |
+- Table size: > 100M rows
+- Query filter: Always on date
+- Data lifecycle: Retention policy
+- Maintenance: Bulk deletes
 
 ### Partition Types
 
@@ -334,27 +338,23 @@ Before production:
 
 ## Anti-Patterns
 
-| ❌ Don't                     | ✅ Do                               |
-| ---------------------------- | ----------------------------------- |
-| Use TIMESTAMP without TZ     | Use TIMESTAMPTZ                     |
-| VARCHAR(n) for variable text | TEXT with CHECK constraints         |
-| SERIAL for IDs               | BIGINT GENERATED ALWAYS AS IDENTITY |
-| JSON type                    | JSONB (indexable, smaller)          |
-| Index every column           | Index query patterns                |
-| Ignore EXPLAIN output        | Analyze before optimizing           |
-| Store arrays for relations   | Use junction tables                 |
-| Mixed-case identifiers       | snake_case (unquoted)               |
+- Use TIMESTAMP without TZ: Use TIMESTAMPTZ
+- VARCHAR(n) for variable text: TEXT with CHECK constraints
+- SERIAL for IDs: BIGINT GENERATED ALWAYS AS IDENTITY
+- JSON type: JSONB (indexable, smaller)
+- Index every column: Index query patterns
+- Ignore EXPLAIN output: Analyze before optimizing
+- Store arrays for relations: Use junction tables
+- Mixed-case identifiers: snake_case (unquoted)
 
 ---
 
 ## Related Skills
 
-| Need              | Skill                   |
-| ----------------- | ----------------------- |
-| General DB design | `database-design`       |
-| API integration   | `api-patterns`          |
-| Query performance | `performance-profiling` |
-| Security patterns | `security-fundamentals` |
+- General DB design: `database-design`
+- API integration: `api-patterns`
+- Query performance: `performance-profiling`
+- Security patterns: `security-fundamentals`
 
 ---
 

package/kits/coder/skills/prompt-engineering/SKILL.md

@@ -8,19 +8,27 @@ priority: CRITICAL
 
 # Prompt Engineering - AI Communication Excellence
 
-> **Philosophy:** Prompts are code. They should be **specific, structured, and testable**. Vague prompts produce vague results.
+## ⚡ Quick Reference
+
+- **Structure**: Role → Task → Format → Constraints → Examples → Output format
+- **Be specific**: Vague prompt = vague output · specify length, format, tone, audience
+- **Chain of Thought**: "Think step by step" for complex reasoning · "First, list..." for structured output
+- **Few-shot**: 2-5 examples beats 1000-word description · Show don't tell
+- **Iteration**: Start simple → add constraints → refine · Save effective prompts as templates
+- **System prompt**: Set persona + rules + format once · User message = task only
+
+---
+
 
 ---
 
 ## Core Principles
 
-| Principle      | Rule                                               |
-| -------------- | -------------------------------------------------- |
-| **Specific**   | Ambiguity causes inconsistent outputs              |
-| **Structured** | Clear sections: Context → Task → Format → Examples |
-| **Testable**   | Evaluate on diverse inputs, measure consistency    |
-| **Iterative**  | Start simple, add complexity only when needed      |
-| **Versioned**  | Treat prompts as code with proper version control  |
+- **Specific**: Ambiguity causes inconsistent outputs
+- **Structured**: Clear sections: Context → Task → Format → Examples
+- **Testable**: Evaluate on diverse inputs, measure consistency
+- **Iterative**: Start simple, add complexity only when needed
+- **Versioned**: Treat prompts as code with proper version control
 
 ---
 
@@ -65,12 +73,10 @@ You are a senior backend engineer specializing in API design.
 
 ### 1. Few-Shot Learning
 
-| When to Use                | Examples Needed    |
-| -------------------------- | ------------------ |
-| Consistent formatting      | 2-3 examples       |
-| Complex reasoning patterns | 3-5 examples       |
-| Edge case handling         | Include edge cases |
-| Simple tasks               | 0-1 examples       |
+- Consistent formatting: 2-3 examples
+- Complex reasoning patterns: 3-5 examples
+- Edge case handling: Include edge cases
+- Simple tasks: 0-1 examples
 
 ```markdown
 Extract key information:
@@ -182,11 +188,9 @@ If uncertain:
 
 ### Token Efficiency
 
-| Inefficient                        | Efficient                        |
-| ---------------------------------- | -------------------------------- |
-| Long verbose instructions          | Concise, direct commands         |
-| Repeating context in every message | System prompt for stable context |
-| 10 examples when 3 suffice         | Minimal effective examples       |
+- Long verbose instructions: Concise, direct commands
+- Repeating context in every message: System prompt for stable context
+- 10 examples when 3 suffice: Minimal effective examples
 
 ---
 
@@ -215,15 +219,13 @@ Task complexity?
 
 ## Anti-Patterns (DON'T)
 
-| ❌ Anti-Pattern                | ✅ Correct Approach               |
-| ------------------------------ | --------------------------------- |
-| Vague instructions             | Specific, measurable requirements |
-| Complex prompt from start      | Start simple, iterate             |
-| Examples that don't match task | Representative, diverse examples  |
-| No output format specified     | Clear format expectations         |
-| Ignoring edge cases            | Test on boundary inputs           |
-| Same prompt for all tasks      | Task-specific optimized prompts   |
-| No version control             | Git-track prompts like code       |
+- Vague instructions: Specific, measurable requirements
+- Complex prompt from start: Start simple, iterate
+- Examples that don't match task: Representative, diverse examples
+- No output format specified: Clear format expectations
+- Ignoring edge cases: Test on boundary inputs
+- Same prompt for all tasks: Task-specific optimized prompts
+- No version control: Git-track prompts like code
 
 ---
 
@@ -252,25 +254,21 @@ Task complexity?
 
 ## 🔴 Self-Check Before Completing
 
-| Check                  | Question                           |
-| ---------------------- | ---------------------------------- |
-| ✅ **Specific?**       | No ambiguous instructions?         |
-| ✅ **Structured?**     | Role → Task → Format → Examples?   |
-| ✅ **Tested?**         | Evaluated on diverse inputs?       |
-| ✅ **Versioned?**      | Prompt tracked in version control? |
-| ✅ **Optimized?**      | Minimal tokens, maximum clarity?   |
-| ✅ **Error handling?** | Handles uncertain/edge cases?      |
+- ✅ **Specific?**: No ambiguous instructions?
+- ✅ **Structured?**: Role → Task → Format → Examples?
+- ✅ **Tested?**: Evaluated on diverse inputs?
+- ✅ **Versioned?**: Prompt tracked in version control?
+- ✅ **Optimized?**: Minimal tokens, maximum clarity?
+- ✅ **Error handling?**: Handles uncertain/edge cases?
 
 ---
 
 ## Related Skills
 
-| Need                    | Skill                    |
-| ----------------------- | ------------------------ |
-| Agent design            | `agent-creator` (future) |
-| Skill creation          | `skill-creator` (future) |
-| AI application patterns | `ai-patterns` (future)   |
-| User communication      | `brainstorming`          |
+- Agent design: `agent-creator` (future)
+- Skill creation: `skill-creator` (future)
+- AI application patterns: `ai-patterns` (future)
+- User communication: `brainstorming`
 
 ---
 

package/kits/coder/skills/queue-patterns/SKILL.md

@@ -7,7 +7,17 @@ tags: [architecture, queue, jobs, async, reliability]
 
 # Queue Patterns - Background Job Processing Skill
 
-> **Purpose:** Enable AI agents to design and implement reliable message queue systems with proper retry strategies, idempotency, and observability.
+## ⚡ Quick Reference
+
+- **System selection**: Node.js → BullMQ · Python → Celery · Serverless → SQS · Multi-lang → RabbitMQ · Streaming → Kafka
+- **Job design**: Small payload (IDs only) · Idempotency key · Include tenant_id/correlation_id · Set timeout
+- **Retry**: Exponential backoff · Max 3-5 attempts · Dead Letter Queue after max retries · DLQ monitored
+- **Idempotency**: Running same job 2x = same result · Check before write · Deduplication key
+- **Concurrency**: Bounded limits · Rate limit external API calls · Separate queues by priority (fast/normal/bulk)
+- **Monitoring**: Queue depth · Processing time · DLQ count · Stalled jobs alerts
+
+---
+
 
 ---
 
@@ -27,13 +37,11 @@ tags: [architecture, queue, jobs, async, reliability]
 
 > **"A queue is a promise: jobs go in, results come out, nothing is lost."**
 
-| Principle                   | Implementation                                           |
-| --------------------------- | -------------------------------------------------------- |
-| **Jobs Are Sacred**         | Every job must complete, fail explicitly, or move to DLQ |
-| **Idempotency by Design**   | Same job running twice = same outcome                    |
-| **Reliability Over Speed**  | Slow and correct beats fast and lossy                    |
-| **Observability Mandatory** | Every job traceable from start to end                    |
-| **Fail Closed**             | Unknown errors → retry, not ignore                       |
+- **Jobs Are Sacred**: Every job must complete, fail explicitly, or move to DLQ
+- **Idempotency by Design**: Same job running twice = same outcome
+- **Reliability Over Speed**: Slow and correct beats fast and lossy
+- **Observability Mandatory**: Every job traceable from start to end
+- **Fail Closed**: Unknown errors → retry, not ignore
 
 ---
 
@@ -169,14 +177,12 @@ WAITING → ACTIVE → COMPLETED
 
 ### Queue Architecture Decisions
 
-| Need                       | Solution                          |
-| -------------------------- | --------------------------------- |
-| Fast priority jobs         | Separate priority queue           |
-| Delayed execution          | Scheduled jobs with `delay`       |
-| Rate limiting external API | Limiter group in BullMQ           |
-| Strict ordering            | FIFO with job grouping            |
-| Large batch processing     | Parent-child jobs (chunking)      |
-| Multi-tenant isolation     | Queue per tenant OR tenant prefix |
+- Fast priority jobs: Separate priority queue
+- Delayed execution: Scheduled jobs with `delay`
+- Rate limiting external API: Limiter group in BullMQ
+- Strict ordering: FIFO with job grouping
+- Large batch processing: Parent-child jobs (chunking)
+- Multi-tenant isolation: Queue per tenant OR tenant prefix
 
 ### Concurrency Patterns
 

package/kits/coder/skills/react-native-patterns/SKILL.md

@@ -8,19 +8,27 @@ priority: MEDIUM
 
 # React Native Patterns - Mobile Excellence with Expo
 
-> **Philosophy:** Use Expo unless you have a very specific reason not to. OTA updates, managed native code, and faster development are worth the trade-offs.
+## ⚡ Quick Reference
+
+- **Framework**: Expo managed → EAS Build → Bare (native modules only)
+- **Lists**: `FlatList`/`FlashList` not `ScrollView` for long lists · `keyExtractor` required
+- **State**: Local → useState · Global → Zustand/Jotai · Server → React Query
+- **Navigation**: expo-router (file-based) or @react-navigation · Always wrap in `NavigationContainer`
+- **Performance**: Reanimated for 60fps animations · `memo` + `useCallback` · `InteractionManager` for heavy ops
+- **Native**: MMKV for fast storage · expo-secure-store for secrets · Test on physical device always
+
+---
+
 
 ---
 
 ## 🎯 Core Principles
 
-| Principle          | Rule                                                  |
-| ------------------ | ----------------------------------------------------- |
-| **Expo First**     | Start with Expo, eject only when absolutely necessary |
-| **Platform Aware** | One codebase, platform-specific polish                |
-| **Offline Ready**  | Assume network is unreliable                          |
-| **Performance**    | FlashList, memoization, native thread animations      |
-| **Type Safe**      | TypeScript is mandatory                               |
+- **Expo First**: Start with Expo, eject only when absolutely necessary
+- **Platform Aware**: One codebase, platform-specific polish
+- **Offline Ready**: Assume network is unreliable
+- **Performance**: FlashList, memoization, native thread animations
+- **Type Safe**: TypeScript is mandatory
 
 ```
 ❌ WRONG: Bare React Native for simple apps
@@ -352,41 +360,35 @@ eas update --branch production --message "Bug fixes"
 
 ## 🚨 Anti-Patterns
 
-| ❌ Don't                     | ✅ Do                                |
-| ---------------------------- | ------------------------------------ |
-| Use FlatList for large lists | Use FlashList                        |
-| Inline styles                | Use StyleSheet.create                |
-| Fetch in render              | Use useEffect or React Query         |
-| Ignore platform differences  | Test on both iOS and Android         |
-| Store secrets in code        | Use environment variables            |
-| Skip error boundaries        | Handle crashes gracefully            |
-| Animate on JS thread         | Use Reanimated for native animations |
-| Forget offline handling      | Implement offline-first              |
+- Use FlatList for large lists: Use FlashList
+- Inline styles: Use StyleSheet.create
+- Fetch in render: Use useEffect or React Query
+- Ignore platform differences: Test on both iOS and Android
+- Store secrets in code: Use environment variables
+- Skip error boundaries: Handle crashes gracefully
+- Animate on JS thread: Use Reanimated for native animations
+- Forget offline handling: Implement offline-first
 
 ---
 
 ## ✅ Self-Check Before Completing
 
-| Check               | Question                                 |
-| ------------------- | ---------------------------------------- |
-| ✅ **Expo?**        | Using Expo unless specifically required? |
-| ✅ **TypeScript?**  | Full type coverage?                      |
-| ✅ **Offline?**     | Handles offline state gracefully?        |
-| ✅ **Platform?**    | Tested on both iOS and Android?          |
-| ✅ **Performance?** | FlashList, memoization, Reanimated?      |
-| ✅ **Secure?**      | Tokens in SecureStore, not AsyncStorage? |
-| ✅ **Navigation?**  | Expo Router properly configured?         |
+- ✅ **Expo?**: Using Expo unless specifically required?
+- ✅ **TypeScript?**: Full type coverage?
+- ✅ **Offline?**: Handles offline state gracefully?
+- ✅ **Platform?**: Tested on both iOS and Android?
+- ✅ **Performance?**: FlashList, memoization, Reanimated?
+- ✅ **Secure?**: Tokens in SecureStore, not AsyncStorage?
+- ✅ **Navigation?**: Expo Router properly configured?
 
 ---
 
 ## 🔗 Related Skills
 
-| Need               | Skill              |
-| ------------------ | ------------------ |
-| Flutter comparison | `flutter-patterns` |
-| Mobile design      | `mobile-design`    |
-| React patterns     | `react-patterns`   |
-| Testing            | `testing-patterns` |
+- Flutter comparison: `flutter-patterns`
+- Mobile design: `mobile-design`
+- React patterns: `react-patterns`
+- Testing: `testing-patterns`
 
 ---