@neyugn/agent-kits 0.5.0 → 0.5.3

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

@@ -6,22 +6,29 @@ allowed-tools: Read, Write, Edit, Glob, Grep, Bash
 
 # AWS Patterns - Cloud Infrastructure Management
 
-> **Philosophy:** Security-first, automation-ready, and production-proven patterns for AWS services.
+## ⚡ Quick Reference
+
+- **IAM**: Least privilege · No root · MFA everywhere · Temporary credentials (STS) · No `"Action": "*"` or `"Resource": "*"`
+- **S3**: Always block public access · Enable versioning + encryption · Use lifecycle policies
+- **EC2**: No `0.0.0.0/0` for SSH (port 22) · IMDSv2 required · EBS encrypted
+- **Lambda**: Least privilege roles · KMS for env vars · VPC config for internal resources
+- **Security**: CloudTrail enabled (multi-region) · All secrets in Secrets Manager not env vars
+- **Deployments**: CloudFormation/Terraform only · Never manual → infra as code
+
+---
 
 ---
 
 ## 📑 Content Map
 
-| Section                 | When to Read                            |
-| ----------------------- | --------------------------------------- |
-| AWS CLI Basics          | Setting up CLI, configuration, profiles |
-| IAM Security Patterns   | Users, roles, policies, access control  |
-| S3 Patterns             | Bucket management, object storage, sync |
-| EC2 Patterns            | Instance management, security groups    |
-| Lambda Patterns         | Serverless functions, deployment        |
-| CloudFormation Patterns | Infrastructure as Code                  |
-| Security Checklist      | Pre-deployment security validation      |
-| Troubleshooting         | Common issues and solutions             |
+- AWS CLI Basics: Setting up CLI, configuration, profiles
+- IAM Security Patterns: Users, roles, policies, access control
+- S3 Patterns: Bucket management, object storage, sync
+- EC2 Patterns: Instance management, security groups
+- Lambda Patterns: Serverless functions, deployment
+- CloudFormation Patterns: Infrastructure as Code
+- Security Checklist: Pre-deployment security validation
+- Troubleshooting: Common issues and solutions
 
 ---
 
@@ -53,12 +60,10 @@ aws sts get-caller-identity
 
 ### Profile Management
 
-| Pattern         | Command                                                                                            |
-| --------------- | -------------------------------------------------------------------------------------------------- |
-| Use profile     | `aws s3 ls --profile production`                                                                   |
-| Export profile  | `export AWS_PROFILE=production`                                                                    |
-| Override region | `aws ec2 describe-instances --region us-west-2`                                                    |
-| MFA session     | `aws sts get-session-token --serial-number arn:aws:iam::123456789012:mfa/user --token-code 123456` |
+- Use profile: `aws s3 ls --profile production`
+- Export profile: `export AWS_PROFILE=production`
+- Override region: `aws ec2 describe-instances --region us-west-2`
+- MFA session: `aws sts get-session-token --serial-number arn:aws:iam::123456789012:mfa/user --token-code 123456`
 
 ### Output Formats
 
@@ -82,13 +87,11 @@ aws ec2 describe-instances | jq '.Reservations[].Instances[].InstanceId'
 
 ### Core Principles (2024-2025)
 
-| Principle                 | Implementation                             |
-| ------------------------- | ------------------------------------------ |
-| **Least Privilege**       | Grant only minimum required permissions    |
-| **Temporary Credentials** | Use IAM roles, avoid long-term access keys |
-| **MFA Everywhere**        | Require MFA for console access + API calls |
-| **No Root User**          | Never use root for daily tasks             |
-| **Regular Audits**        | Review unused roles/users every 90 days    |
+- **Least Privilege**: Grant only minimum required permissions
+- **Temporary Credentials**: Use IAM roles, avoid long-term access keys
+- **MFA Everywhere**: Require MFA for console access + API calls
+- **No Root User**: Never use root for daily tasks
+- **Regular Audits**: Review unused roles/users every 90 days
 
 ### IAM User Management
 
@@ -155,13 +158,11 @@ aws sts assume-role \
 
 ### Policy Best Practices
 
-| ❌ Don't             | ✅ Do                  |
-| -------------------- | ---------------------- |
-| `"Resource": "*"`    | Specify exact ARNs     |
-| `"Action": "*"`      | List specific actions  |
-| Attach to users      | Attach to groups/roles |
-| Hardcode credentials | Use IAM roles + STS    |
-| Skip MFA for admins  | Require MFA always     |
+- `"Resource": "*"`: Specify exact ARNs
+- `"Action": "*"`: List specific actions
+- Attach to users: Attach to groups/roles
+- Hardcode credentials: Use IAM roles + STS
+- Skip MFA for admins: Require MFA always
 
 ---
 
@@ -524,14 +525,12 @@ aws logs put-retention-policy \
 
 ## 🔧 Troubleshooting
 
-| Issue                          | Solution                                                        |
-| ------------------------------ | --------------------------------------------------------------- |
-| `Unable to locate credentials` | Run `aws configure` or check `~/.aws/credentials`               |
-| `Access Denied`                | Check IAM policy, verify resource ARN, check STS assume-role    |
-| `Region not specified`         | Add `--region` flag or set `AWS_DEFAULT_REGION`                 |
-| `Invalid JSON`                 | Use `--cli-binary-format raw-in-base64-out` for Lambda payloads |
-| `ExpiredToken`                 | Get new STS session token if using MFA/assumed role             |
-| `NoSuchBucket`                 | Check bucket name and region, S3 is globally unique             |
+- `Unable to locate credentials`: Run `aws configure` or check `~/.aws/credentials`
+- `Access Denied`: Check IAM policy, verify resource ARN, check STS assume-role
+- `Region not specified`: Add `--region` flag or set `AWS_DEFAULT_REGION`
+- `Invalid JSON`: Use `--cli-binary-format raw-in-base64-out` for Lambda payloads
+- `ExpiredToken`: Get new STS session token if using MFA/assumed role
+- `NoSuchBucket`: Check bucket name and region, S3 is globally unique
 
 ### Debug Mode
 
@@ -547,29 +546,25 @@ aws s3 ls --debug 2>&1 | grep "Making request"
 
 ## Anti-Patterns
 
-| ❌ Don't                     | ✅ Do                                          |
-| ---------------------------- | ---------------------------------------------- |
-| Hardcode access keys in code | Use IAM roles for EC2/Lambda                   |
-| Use `0.0.0.0/0` for SSH      | Restrict to specific IP ranges                 |
-| Create access keys for root  | Never use root, use IAM users                  |
-| Skip MFA for admin accounts  | Require MFA for all privileged access          |
-| Use long-term credentials    | Prefer STS temporary credentials               |
-| Store secrets in env vars    | Use AWS Secrets Manager or SSM Parameter Store |
-| Manual deployments           | Use CloudFormation/Terraform/CDK               |
-| Single region deployment     | Multi-region for DR-critical apps              |
+- Hardcode access keys in code: Use IAM roles for EC2/Lambda
+- Use `0.0.0.0/0` for SSH: Restrict to specific IP ranges
+- Create access keys for root: Never use root, use IAM users
+- Skip MFA for admin accounts: Require MFA for all privileged access
+- Use long-term credentials: Prefer STS temporary credentials
+- Store secrets in env vars: Use AWS Secrets Manager or SSM Parameter Store
+- Manual deployments: Use CloudFormation/Terraform/CDK
+- Single region deployment: Multi-region for DR-critical apps
 
 ---
 
 ## Related Skills
 
-| Need                   | Skill                      |
-| ---------------------- | -------------------------- |
-| Infrastructure as Code | `terraform-patterns`       |
-| Kubernetes on AWS      | `kubernetes-patterns`      |
-| Docker/ECS             | `docker-patterns`          |
-| CI/CD with AWS         | `github-actions`           |
-| Security hardening     | `security-fundamentals`    |
-| Monitoring             | `monitoring-observability` |
+- Infrastructure as Code: `terraform-patterns`
+- Kubernetes on AWS: `kubernetes-patterns`
+- Docker/ECS: `docker-patterns`
+- CI/CD with AWS: `github-actions`
+- Security hardening: `security-fundamentals`
+- Monitoring: `monitoring-observability`
 
 ---
 

package/kits/coder/skills/brainstorming/SKILL.md

@@ -6,7 +6,16 @@ allowed-tools: Read, Write, Edit
 
 # Brainstorming - Socratic Discovery Protocol
 
-> **Philosophy:** Understanding precedes implementation. Ask first, build second.
+## ⚡ Quick Reference
+
+- **Ask before build**: New feature/vague request → Stop and ask 3+ clarifying questions first
+- **Socratic questions**: Goal · Users · Scope · Constraints · Priority (MVP vs nice-to-have)
+- **Never assume**: 1% unclear → ask · Assumptions cause rework
+- **Context gathering**: Purpose → Users → Scope → Constraints → then plan
+- **Output**: Clear requirements doc before any implementation begins
+
+---
+
 
 ---
 
@@ -290,16 +299,14 @@ Surface hidden assumptions before implementation
 
 ## 🚨 Anti-Patterns
 
-| ❌ Don't                        | ✅ Do                                                |
-| ------------------------------- | ---------------------------------------------------- |
-| Ask 10+ questions at once       | Group into 3-5 most important                        |
-| Ask obvious questions           | Ask where there's genuine ambiguity                  |
-| Re-ask answered questions       | Read conversation context                            |
-| Block on every detail           | Make reasonable default assumptions for minor things |
-| Question simple requests        | Apply judgment on when questions add value           |
-| Ask then ignore answers         | Incorporate answers into your approach               |
-| Pretend to understand           | Admit confusion and ask for clarity                  |
-| Assume user knows best approach | Offer expert guidance with questions                 |
+- Ask 10+ questions at once: Group into 3-5 most important
+- Ask obvious questions: Ask where there's genuine ambiguity
+- Re-ask answered questions: Read conversation context
+- Block on every detail: Make reasonable default assumptions for minor things
+- Question simple requests: Apply judgment on when questions add value
+- Ask then ignore answers: Incorporate answers into your approach
+- Pretend to understand: Admit confusion and ask for clarity
+- Assume user knows best approach: Offer expert guidance with questions
 
 ---
 
@@ -347,23 +354,19 @@ Before major implementation:
 
 **Question effectiveness:**
 
-| Question Type | When Valuable                       |
-| ------------- | ----------------------------------- |
-| Clarifying    | When terms are ambiguous            |
-| Probing       | When surface answer is insufficient |
-| Hypothetical  | When exploring edge cases           |
-| Comparative   | When choosing between options       |
-| Reflective    | When validating understanding       |
+- Clarifying: When terms are ambiguous
+- Probing: When surface answer is insufficient
+- Hypothetical: When exploring edge cases
+- Comparative: When choosing between options
+- Reflective: When validating understanding
 
 ---
 
 ## 🔗 Related Skills
 
-| Need                         | Skill                  |
-| ---------------------------- | ---------------------- |
-| Writing implementation plans | `plan-writing`         |
-| Debugging with questions     | `systematic-debugging` |
-| Clean code standards         | `clean-code`           |
+- Writing implementation plans: `plan-writing`
+- Debugging with questions: `systematic-debugging`
+- Clean code standards: `clean-code`
 
 ---
 

package/kits/coder/skills/clean-code/SKILL.md

@@ -8,32 +8,36 @@ priority: CRITICAL
 
 # Clean Code - Pragmatic AI Coding Standards
 
-> **Philosophy:** Be **concise, direct, and solution-focused**. The user wants working code, not programming lessons.
+## ⚡ Quick Reference
+
+- **SRP + DRY + KISS**: 1 function = 1 thing · no duplication · simplest solution
+- **Naming**: `verb+noun` functions · `noun` variables · `is/has` booleans · no abbreviations
+- **Functions**: ≤20 lines · ≤3 params · return early · no side effects hidden
+- **No over-engineering**: No abstractions without 3+ uses · No premature optimization
+- **Error handling**: Never silent catch · always typed errors · fail fast
+
+---
 
 ---
 
 ## Core Principles
 
-| Principle     | Rule                                                       |
-| ------------- | ---------------------------------------------------------- |
-| **SRP**       | Single Responsibility - each function/class does ONE thing |
-| **DRY**       | Don't Repeat Yourself - extract duplicates, reuse          |
-| **KISS**      | Keep It Simple - simplest solution that works              |
-| **YAGNI**     | You Aren't Gonna Need It - don't build unused features     |
-| **Boy Scout** | Leave code cleaner than you found it                       |
+- **SRP**: Single Responsibility - each function/class does ONE thing
+- **DRY**: Don't Repeat Yourself - extract duplicates, reuse
+- **KISS**: Keep It Simple - simplest solution that works
+- **YAGNI**: You Aren't Gonna Need It - don't build unused features
+- **Boy Scout**: Leave code cleaner than you found it
 
 ---
 
 ## Naming Rules
 
-| Element       | Convention                                            |
-| ------------- | ----------------------------------------------------- |
-| **Variables** | Reveal intent: `userCount` not `n`                    |
-| **Functions** | Verb + noun: `getUserById()` not `user()`             |
-| **Booleans**  | Question form: `isActive`, `hasPermission`, `canEdit` |
-| **Constants** | SCREAMING_SNAKE: `MAX_RETRY_COUNT`                    |
-| **Classes**   | PascalCase nouns: `UserService`, `PaymentGateway`     |
-| **Files**     | kebab-case or camelCase based on project convention   |
+- **Variables**: Reveal intent: `userCount` not `n`
+- **Functions**: Verb + noun: `getUserById()` not `user()`
+- **Booleans**: Question form: `isActive`, `hasPermission`, `canEdit`
+- **Constants**: SCREAMING_SNAKE: `MAX_RETRY_COUNT`
+- **Classes**: PascalCase nouns: `UserService`, `PaymentGateway`
+- **Files**: kebab-case or camelCase based on project convention
 
 > **Rule:** If you need a comment to explain a name, rename it.
 
@@ -41,26 +45,22 @@ priority: CRITICAL
 
 ## Function Rules
 
-| Rule                   | Description                           |
-| ---------------------- | ------------------------------------- |
-| **Small**              | Max 20 lines, ideally 5-10            |
-| **One Thing**          | Does one thing, does it well          |
-| **One Level**          | One level of abstraction per function |
-| **Few Args**           | Max 3 arguments, prefer 0-2           |
-| **No Side Effects**    | Don't mutate inputs unexpectedly      |
-| **Pure When Possible** | Same input → same output              |
+- **Small**: Max 20 lines, ideally 5-10
+- **One Thing**: Does one thing, does it well
+- **One Level**: One level of abstraction per function
+- **Few Args**: Max 3 arguments, prefer 0-2
+- **No Side Effects**: Don't mutate inputs unexpectedly
+- **Pure When Possible**: Same input → same output
 
 ---
 
 ## Code Structure
 
-| Pattern            | Apply                                     |
-| ------------------ | ----------------------------------------- |
-| **Guard Clauses**  | Early returns for edge cases              |
-| **Flat > Nested**  | Avoid deep nesting (max 2 levels)         |
-| **Composition**    | Small functions composed together         |
-| **Colocation**     | Keep related code close                   |
-| **Vertical Slice** | Feature files together, not by layer type |
+- **Guard Clauses**: Early returns for edge cases
+- **Flat > Nested**: Avoid deep nesting (max 2 levels)
+- **Composition**: Small functions composed together
+- **Colocation**: Keep related code close
+- **Vertical Slice**: Feature files together, not by layer type
 
 ### Guard Clause Example
 
@@ -90,33 +90,27 @@ function processUser(user) {
 
 ## AI Coding Style
 
-| Situation                 | Action                                     |
-| ------------------------- | ------------------------------------------ |
-| User asks for feature     | Write it directly                          |
-| User reports bug          | Fix it, don't explain first                |
-| No clear requirement      | Ask, don't assume                          |
-| Multiple valid approaches | Pick one, mention alternatives if critical |
+- User asks for feature: Write it directly
+- User reports bug: Fix it, don't explain first
+- No clear requirement: Ask, don't assume
+- Multiple valid approaches: Pick one, mention alternatives if critical
 
 ### Output Quality Rules
 
-| Rule                 | Description                                 |
-| -------------------- | ------------------------------------------- |
-| **No Preamble**      | Skip "Here's the code..." - just write code |
-| **No Postamble**     | Skip "This code does..." - let code speak   |
-| **Minimal Comments** | Only for complex/non-obvious business logic |
-| **Complete Code**    | No `// ... rest of code` placeholders       |
-| **Test Immediately** | Run/verify code before claiming complete    |
+- **No Preamble**: Skip "Here's the code..." - just write code
+- **No Postamble**: Skip "This code does..." - let code speak
+- **Minimal Comments**: Only for complex/non-obvious business logic
+- **Complete Code**: No `// ... rest of code` placeholders
+- **Test Immediately**: Run/verify code before claiming complete
 
 ---
 
 ## Error Handling Patterns
 
-| Pattern            | When to Use                             |
-| ------------------ | --------------------------------------- |
-| **Return Early**   | Validation failures, missing data       |
-| **Throw Specific** | Domain errors, use custom error classes |
-| **Try/Catch**      | External calls, I/O operations          |
-| **Result Type**    | Complex operations, functional style    |
+- **Return Early**: Validation failures, missing data
+- **Throw Specific**: Domain errors, use custom error classes
+- **Try/Catch**: External calls, I/O operations
+- **Result Type**: Complex operations, functional style
 
 ### Error Handling Example
 
@@ -133,18 +127,16 @@ throw new InsufficientFundsError(amount, balance);
 
 ## Anti-Patterns (DON'T)
 
-| ❌ Pattern                  | ✅ Fix                  |
-| --------------------------- | ----------------------- |
-| Comment every line          | Delete obvious comments |
-| Helper for one-liner        | Inline the code         |
-| Factory for 2 objects       | Direct instantiation    |
-| utils.ts with 1 function    | Put code where used     |
-| "First we import..."        | Just write code         |
-| Deep nesting (3+ levels)    | Guard clauses           |
-| Magic numbers               | Named constants         |
-| God functions (50+ lines)   | Split by responsibility |
-| Premature optimization      | Make it work first      |
-| Helper folder with 20 files | Colocate with features  |
+- Comment every line: Delete obvious comments
+- Helper for one-liner: Inline the code
+- Factory for 2 objects: Direct instantiation
+- utils.ts with 1 function: Put code where used
+- "First we import...": Just write code
+- Deep nesting (3+ levels): Guard clauses
+- Magic numbers: Named constants
+- God functions (50+ lines): Split by responsibility
+- Premature optimization: Make it work first
+- Helper folder with 20 files: Colocate with features
 
 ---
 
@@ -152,12 +144,10 @@ throw new InsufficientFundsError(amount, balance);
 
 **Before changing a file, ask yourself:**
 
-| Question                        | Why                      |
-| ------------------------------- | ------------------------ |
-| **What imports this file?**     | They might break         |
-| **What does this file import?** | Interface changes        |
-| **What tests cover this?**      | Tests might fail         |
-| **Is this a shared component?** | Multiple places affected |
+- **What imports this file?**: They might break
+- **What does this file import?**: Interface changes
+- **What tests cover this?**: Tests might fail
+- **Is this a shared component?**: Multiple places affected
 
 **Quick Check:**
 
@@ -174,15 +164,13 @@ File to edit: UserService.ts
 
 ## Summary
 
-| Do                     | Don't                      |
-| ---------------------- | -------------------------- |
-| Write code directly    | Write tutorials            |
-| Let code self-document | Add obvious comments       |
-| Fix bugs immediately   | Explain the fix first      |
-| Inline small things    | Create unnecessary files   |
-| Name things clearly    | Use abbreviations          |
-| Keep functions small   | Write 100+ line functions  |
-| Verify code works      | Claim done without testing |
+- Write code directly: Write tutorials
+- Let code self-document: Add obvious comments
+- Fix bugs immediately: Explain the fix first
+- Inline small things: Create unnecessary files
+- Name things clearly: Use abbreviations
+- Keep functions small: Write 100+ line functions
+- Verify code works: Claim done without testing
 
 ---
 
@@ -190,13 +178,11 @@ File to edit: UserService.ts
 
 **Before saying "task complete", verify:**
 
-| Check                     | Question                          |
-| ------------------------- | --------------------------------- |
-| ✅ **Goal met?**          | Did I do exactly what user asked? |
-| ✅ **Files edited?**      | Did I modify all necessary files? |
-| ✅ **Code works?**        | Did I test/verify the change?     |
-| ✅ **No errors?**         | Lint and TypeScript pass?         |
-| ✅ **Nothing forgotten?** | Any edge cases missed?            |
+- ✅ **Goal met?**: Did I do exactly what user asked?
+- ✅ **Files edited?**: Did I modify all necessary files?
+- ✅ **Code works?**: Did I test/verify the change?
+- ✅ **No errors?**: Lint and TypeScript pass?
+- ✅ **Nothing forgotten?**: Any edge cases missed?
 
 > 🔴 **Rule:** If ANY check fails, fix it before completing.
 
@@ -228,12 +214,10 @@ Is logic non-obvious?
 
 ## Related Skills
 
-| Need                 | Skill                  |
-| -------------------- | ---------------------- |
-| API design patterns  | `api-patterns`         |
-| Testing methodology  | `testing-patterns`     |
-| Systematic debugging | `systematic-debugging` |
-| Database design      | `database-design`      |
+- API design patterns: `api-patterns`
+- Testing methodology: `testing-patterns`
+- Systematic debugging: `systematic-debugging`
+- Database design: `database-design`
 
 ---
 

package/kits/coder/skills/database-design/SKILL.md

@@ -7,7 +7,16 @@ version: 2.0
 
 # Database Design - Principles & Decision Making
 
-> **Philosophy:** Choose the right database and design for the context. Learn to THINK, not copy SQL patterns.
+## ⚡ Quick Reference
+
+- **DB selection**: Prototype → SQLite · Standard → PostgreSQL · Serverless → Neon · AI/embeddings → PG+pgvector
+- **ORM**: TS+DX → Prisma · TS+Edge/perf → Drizzle · Python → SQLAlchemy 2.0
+- **Schema**: 3NF normalization · UUIDs for distributed/exposed · CUID2/ULID for sortable · soft deletes with `deleted_at`
+- **Indexes**: Every FK · every WHERE column · composite = leftmost rule · use `EXPLAIN ANALYZE`
+- **Migrations**: Reversible · test on staging first · backup before prod · `ADD NULLABLE` before `NOT NULL`
+- **N+1**: Use `include`/joins · batch requests · avoid row-per-row loops
+
+---
 
 ---
 
@@ -54,13 +63,11 @@ What are your requirements?
 
 ### When to Denormalize
 
-| Scenario                      | Consider Denormalization |
-| ----------------------------- | ------------------------ |
-| Frequent JOINs on same tables | ✅ Yes                   |
-| Read-heavy workload           | ✅ Yes                   |
-| Real-time analytics           | ✅ Yes                   |
-| Write-heavy workload          | ❌ No                    |
-| Data integrity critical       | ❌ No                    |
+- Frequent JOINs on same tables: ✅ Yes
+- Read-heavy workload: ✅ Yes
+- Real-time analytics: ✅ Yes
+- Write-heavy workload: ❌ No
+- Data integrity critical: ❌ No
 
 ---
 
@@ -94,13 +101,11 @@ What are your requirements?
 
 ### Indexing Rules
 
-| ✅ Index                 | ❌ Don't Index               |
-| ------------------------ | ---------------------------- |
-| WHERE clause columns     | Low cardinality (bool, enum) |
-| JOIN condition columns   | Frequently updated columns   |
-| ORDER BY columns         | Small tables (<1000 rows)    |
-| Foreign keys             | Columns rarely queried       |
-| High cardinality columns | Already indexed via PK       |
+- WHERE clause columns: Low cardinality (bool, enum)
+- JOIN condition columns: Frequently updated columns
+- ORDER BY columns: Small tables (<1000 rows)
+- Foreign keys: Columns rarely queried
+- High cardinality columns: Already indexed via PK
 
 ### Composite Index Order
 
@@ -213,16 +218,14 @@ EXPLAIN ANALYZE SELECT * FROM users WHERE email = 'test@example.com';
 
 ## Anti-Patterns
 
-| ❌ Don't                             | ✅ Do                    |
-| ------------------------------------ | ------------------------ |
-| Default to PostgreSQL for everything | Choose based on needs    |
-| Use `SELECT *` in production         | Select specific columns  |
-| Skip indexing                        | Index WHERE/JOIN columns |
-| Store structured data as JSON        | Use proper columns       |
-| Ignore N+1 queries                   | Use eager loading        |
-| Run migrations without testing       | Test on prod-like data   |
-| Store dates as strings               | Use proper DATE types    |
-| No foreign key constraints           | Define relationships     |
+- Default to PostgreSQL for everything: Choose based on needs
+- Use `SELECT *` in production: Select specific columns
+- Skip indexing: Index WHERE/JOIN columns
+- Store structured data as JSON: Use proper columns
+- Ignore N+1 queries: Use eager loading
+- Run migrations without testing: Test on prod-like data
+- Store dates as strings: Use proper DATE types
+- No foreign key constraints: Define relationships
 
 ---
 
@@ -243,12 +246,10 @@ Before implementation:
 
 ## Related Skills
 
-| Need              | Skill                   |
-| ----------------- | ----------------------- |
-| API design        | `api-patterns`          |
-| Backend patterns  | `nodejs-best-practices` |
-| Query performance | `performance-profiling` |
-| Security          | `security-fundamentals` |
+- API design: `api-patterns`
+- Backend patterns: `nodejs-best-practices`
+- Query performance: `performance-profiling`
+- Security: `security-fundamentals`
 
 ---