zsp/everything-claude-code
1
0
Fork 0
mirror of https://github.com/affaan-m/everything-claude-code.git synced 2026-04-09 19:03:28 +08:00
Code Issues Packages Projects Releases Wiki Activity

refactor(rules): restructure into common + language-specific directories

Browse Source 
* refactor(rules): restructure rules into common + language-specific directories

- Split 8 flat rule files into common/, typescript/, python/, golang/
- common/ contains language-agnostic principles (no code examples)
- typescript/ extracts TS/JS specifics (Zod, Playwright, Prettier hooks, etc.)
- python/ adds Python rules (PEP 8, pytest, black/ruff, bandit)
- golang/ adds Go rules (gofmt, table-driven tests, gosec, functional options)
- Replace deprecated ultrathink with extended thinking documentation
- Add README.md with installation guide and new-language template

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

* Fix installation commands for rules

Updated installation instructions to copy all rules to a single directory.

* docs: update README.md to reflect new rules directory structure

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

---------

Co-authored-by: Hor1zonZzz <Hor1zonZzz@users.noreply.github.com>
Co-authored-by: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Hor1zonZzz
2026-02-05 21:58:06 +08:00
committed by GitHub
parent 90ad4edb1f
commit 86b5a53e5d
26 changed files with 580 additions and 135 deletions
Download Patch File Download Diff File Expand all files Collapse all files

56
README.md
View File

@@ -83,8 +83,13 @@ Get up and running in under 2 minutes:
# Clone the repo first # Clone the repo first
git clone https://github.com/affaan-m/everything-claude-code.git git clone https://github.com/affaan-m/everything-claude-code.git
# Copy rules (applies to all projects) # Install common rules (required)
cp -r everything-claude-code/rules/* ~/.claude/rules/ cp -r everything-claude-code/rules/common/* ~/.claude/rules/
# Install language-specific rules (pick your stack)
cp -r everything-claude-code/rules/typescript/* ~/.claude/rules/
cp -r everything-claude-code/rules/python/* ~/.claude/rules/
cp -r everything-claude-code/rules/golang/* ~/.claude/rules/
``` ```
### Step 3: Start Using ### Step 3: Start Using
@@ -195,12 +200,19 @@ everything-claude-code/
| |-- evolve.md # /evolve - Cluster instincts into skills (NEW) | |-- evolve.md # /evolve - Cluster instincts into skills (NEW)
| |
|-- rules/ # Always-follow guidelines (copy to ~/.claude/rules/) |-- rules/ # Always-follow guidelines (copy to ~/.claude/rules/)
| |-- security.md # Mandatory security checks | |-- README.md # Structure overview and installation guide
| |-- coding-style.md # Immutability, file organization | |-- common/ # Language-agnostic principles
| |-- testing.md # TDD, 80% coverage requirement | | |-- coding-style.md # Immutability, file organization
| |-- git-workflow.md # Commit format, PR process | | |-- git-workflow.md # Commit format, PR process
| |-- agents.md # When to delegate to subagents | | |-- testing.md # TDD, 80% coverage requirement
| |-- performance.md # Model selection, context management | | |-- performance.md # Model selection, context management
| | |-- patterns.md # Design patterns, skeleton projects
| | |-- hooks.md # Hook architecture, TodoWrite
| | |-- agents.md # When to delegate to subagents
| | |-- security.md # Mandatory security checks
| |-- typescript/ # TypeScript/JavaScript specific
| |-- python/ # Python specific
| |-- golang/ # Go specific
| |
|-- hooks/ # Trigger-based automations |-- hooks/ # Trigger-based automations
| |-- hooks.json # All hooks config (PreToolUse, PostToolUse, Stop, etc.) | |-- hooks.json # All hooks config (PreToolUse, PostToolUse, Stop, etc.)
@@ -359,11 +371,15 @@ This gives you instant access to all commands, agents, skills, and hooks.
> git clone https://github.com/affaan-m/everything-claude-code.git > git clone https://github.com/affaan-m/everything-claude-code.git
> >
> # Option A: User-level rules (applies to all projects) > # Option A: User-level rules (applies to all projects)
> cp -r everything-claude-code/rules/* ~/.claude/rules/ > cp -r everything-claude-code/rules/common/* ~/.claude/rules/
> cp -r everything-claude-code/rules/typescript/* ~/.claude/rules/ # pick your stack
> cp -r everything-claude-code/rules/python/* ~/.claude/rules/
> cp -r everything-claude-code/rules/golang/* ~/.claude/rules/
> >
> # Option B: Project-level rules (applies to current project only) > # Option B: Project-level rules (applies to current project only)
> mkdir -p .claude/rules > mkdir -p .claude/rules
> cp -r everything-claude-code/rules/* .claude/rules/ > cp -r everything-claude-code/rules/common/* .claude/rules/
> cp -r everything-claude-code/rules/typescript/* .claude/rules/ # pick your stack
> ``` > ```
--- ---
@@ -379,8 +395,11 @@ git clone https://github.com/affaan-m/everything-claude-code.git
# Copy agents to your Claude config # Copy agents to your Claude config
cp everything-claude-code/agents/*.md ~/.claude/agents/ cp everything-claude-code/agents/*.md ~/.claude/agents/
# Copy rules # Copy rules (common + language-specific)
cp everything-claude-code/rules/*.md ~/.claude/rules/ cp -r everything-claude-code/rules/common/* ~/.claude/rules/
cp -r everything-claude-code/rules/typescript/* ~/.claude/rules/ # pick your stack
cp -r everything-claude-code/rules/python/* ~/.claude/rules/
cp -r everything-claude-code/rules/golang/* ~/.claude/rules/
# Copy commands # Copy commands
cp everything-claude-code/commands/*.md ~/.claude/commands/ cp everything-claude-code/commands/*.md ~/.claude/commands/
@@ -448,15 +467,18 @@ Hooks fire on tool events. Example - warn about console.log:
### Rules ### Rules
Rules are always-follow guidelines. Keep them modular: Rules are always-follow guidelines, organized into `common/` (language-agnostic) + language-specific directories:
``` ```
~/.claude/rules/ rules/
security.md # No hardcoded secrets common/ # Universal principles (always install)
coding-style.md # Immutability, file limits typescript/ # TS/JS specific patterns and tools
testing.md # TDD, coverage requirements python/ # Python specific patterns and tools
golang/ # Go specific patterns and tools
``` ```
See [`rules/README.md`](rules/README.md) for installation and structure details.
--- ---
## 🧪 Running Tests ## 🧪 Running Tests

63
rules/README.md Normal file
View File

@@ -0,0 +1,63 @@
# Rules
## Structure
Rules are organized into a **common** layer plus **language-specific** directories:
```
rules/
├── common/ # Language-agnostic principles (always install)
│ ├── coding-style.md
│ ├── git-workflow.md
│ ├── testing.md
│ ├── performance.md
│ ├── patterns.md
│ ├── hooks.md
│ ├── agents.md
│ └── security.md
├── typescript/ # TypeScript/JavaScript specific
├── python/ # Python specific
└── golang/ # Go specific
```
- **common/** contains universal principles — no language-specific code examples.
- **Language directories** extend the common rules with framework-specific patterns, tools, and code examples. Each file references its common counterpart.
## Installation
```bash
# Install common rules (required for all projects)
cp -r rules/common/* ~/.claude/rules/
# Install language-specific rules based on your project's tech stack
cp -r rules/typescript/* ~/.claude/rules/
cp -r rules/python/* ~/.claude/rules/
cp -r rules/golang/* ~/.claude/rules/
# Attention ! ! ! Configure according to your actual project requirements; the configuration here is for reference only.
```
## Rules vs Skills
- **Rules** define standards, conventions, and checklists that apply broadly (e.g., "80% test coverage", "no hardcoded secrets").
- **Skills** (`skills/` directory) provide deep, actionable reference material for specific tasks (e.g., `python-patterns`, `golang-testing`).
Language-specific rule files reference relevant skills where appropriate. Rules tell you *what* to do; skills tell you *how* to do it.
## Adding a New Language
To add support for a new language (e.g., `rust/`):
1. Create a `rules/rust/` directory
2. Add files that extend the common rules:
- `coding-style.md` — formatting tools, idioms, error handling patterns
- `testing.md` — test framework, coverage tools, test organization
- `patterns.md` — language-specific design patterns
- `hooks.md` — PostToolUse hooks for formatters, linters, type checkers
- `security.md` — secret management, security scanning tools
3. Each file should start with:
```
> This file extends [common/xxx.md](../common/xxx.md) with <Language> specific content.
```
4. Reference existing skills if available, or create new ones under `skills/`.

70
rules/coding-style.md
View File

@@ -1,70 +0,0 @@
# Coding Style
## Immutability (CRITICAL)
ALWAYS create new objects, NEVER mutate:
```javascript
// WRONG: Mutation
function updateUser(user, name) {
user.name = name // MUTATION!
return user
}
// CORRECT: Immutability
function updateUser(user, name) {
return {
...user,
name
}
}
```
## File Organization
MANY SMALL FILES > FEW LARGE FILES:
- High cohesion, low coupling
- 200-400 lines typical, 800 max
- Extract utilities from large components
- Organize by feature/domain, not by type
## Error Handling
ALWAYS handle errors comprehensively:
```typescript
try {
const result = await riskyOperation()
return result
} catch (error) {
console.error('Operation failed:', error)
throw new Error('Detailed user-friendly message')
}
```
## Input Validation
ALWAYS validate user input:
```typescript
import { z } from 'zod'
const schema = z.object({
email: z.string().email(),
age: z.number().int().min(0).max(150)
})
const validated = schema.parse(input)
```
## Code Quality Checklist
Before marking work complete:
- [ ] Code is readable and well-named
- [ ] Functions are small (<50 lines)
- [ ] Files are focused (<800 lines)
- [ ] No deep nesting (>4 levels)
- [ ] Proper error handling
- [ ] No console.log statements
- [ ] No hardcoded values
- [ ] No mutation (immutable patterns used)

4
rules/agents.md → rules/common/agents.md
View File

@@ -31,9 +31,9 @@ ALWAYS use parallel Task execution for independent operations:
```markdown ```markdown
# GOOD: Parallel execution # GOOD: Parallel execution
Launch 3 agents in parallel: Launch 3 agents in parallel:
1. Agent 1: Security analysis of auth.ts 1. Agent 1: Security analysis of auth module
2. Agent 2: Performance review of cache system 2. Agent 2: Performance review of cache system
3. Agent 3: Type checking of utils.ts 3. Agent 3: Type checking of utilities
# BAD: Sequential when unnecessary # BAD: Sequential when unnecessary
First agent 1, then agent 2, then agent 3 First agent 1, then agent 2, then agent 3

48
rules/common/coding-style.md Normal file
View File

@@ -0,0 +1,48 @@
# Coding Style
## Immutability (CRITICAL)
ALWAYS create new objects, NEVER mutate existing ones:
```
// Pseudocode
WRONG: modify(original, field, value) → changes original in-place
CORRECT: update(original, field, value) → returns new copy with change
```
Rationale: Immutable data prevents hidden side effects, makes debugging easier, and enables safe concurrency.
## File Organization
MANY SMALL FILES > FEW LARGE FILES:
- High cohesion, low coupling
- 200-400 lines typical, 800 max
- Extract utilities from large modules
- Organize by feature/domain, not by type
## Error Handling
ALWAYS handle errors comprehensively:
- Handle errors explicitly at every level
- Provide user-friendly error messages in UI-facing code
- Log detailed error context on the server side
- Never silently swallow errors
## Input Validation
ALWAYS validate at system boundaries:
- Validate all user input before processing
- Use schema-based validation where available
- Fail fast with clear error messages
- Never trust external data (API responses, user input, file content)
## Code Quality Checklist
Before marking work complete:
- [ ] Code is readable and well-named
- [ ] Functions are small (<50 lines)
- [ ] Files are focused (<800 lines)
- [ ] No deep nesting (>4 levels)
- [ ] Proper error handling
- [ ] No hardcoded values (use constants or config)
- [ ] No mutation (immutable patterns used)

0
rules/git-workflow.md → rules/common/git-workflow.md
View File

16
rules/hooks.md → rules/common/hooks.md
View File

@@ -6,22 +6,6 @@
- **PostToolUse**: After tool execution (auto-format, checks) - **PostToolUse**: After tool execution (auto-format, checks)
- **Stop**: When session ends (final verification) - **Stop**: When session ends (final verification)
## Current Hooks (in ~/.claude/settings.json)
### PreToolUse
- **tmux reminder**: Suggests tmux for long-running commands (npm, pnpm, yarn, cargo, etc.)
- **git push review**: Opens Zed for review before push
- **doc blocker**: Blocks creation of unnecessary .md/.txt files
### PostToolUse
- **PR creation**: Logs PR URL and GitHub Actions status
- **Prettier**: Auto-formats JS/TS files after edit
- **TypeScript check**: Runs tsc after editing .ts/.tsx files
- **console.log warning**: Warns about console.log in edited files
### Stop
- **console.log audit**: Checks all modified files for console.log before session ends
## Auto-Accept Permissions ## Auto-Accept Permissions
Use with caution: Use with caution:

31
rules/common/patterns.md Normal file
View File

@@ -0,0 +1,31 @@
# Common Patterns
## Skeleton Projects
When implementing new functionality:
1. Search for battle-tested skeleton projects
2. Use parallel agents to evaluate options:
- Security assessment
- Extensibility analysis
- Relevance scoring
- Implementation planning
3. Clone best match as foundation
4. Iterate within proven structure
## Design Patterns
### Repository Pattern
Encapsulate data access behind a consistent interface:
- Define standard operations: findAll, findById, create, update, delete
- Concrete implementations handle storage details (database, API, file, etc.)
- Business logic depends on the abstract interface, not the storage mechanism
- Enables easy swapping of data sources and simplifies testing with mocks
### API Response Format
Use a consistent envelope for all API responses:
- Include a success/status indicator
- Include the data payload (nullable on error)
- Include an error message field (nullable on success)
- Include metadata for paginated responses (total, page, limit)

16
rules/performance.md → rules/common/performance.md
View File

@@ -30,13 +30,21 @@ Lower context sensitivity tasks:
- Documentation updates - Documentation updates
- Simple bug fixes - Simple bug fixes
## Ultrathink + Plan Mode ## Extended Thinking + Plan Mode
Extended thinking is enabled by default, reserving up to 31,999 tokens for internal reasoning.
Control extended thinking via:
- **Toggle**: Option+T (macOS) / Alt+T (Windows/Linux)
- **Config**: Set `alwaysThinkingEnabled` in `~/.claude/settings.json`
- **Budget cap**: `export MAX_THINKING_TOKENS=10000`
- **Verbose mode**: Ctrl+O to see thinking output
For complex tasks requiring deep reasoning: For complex tasks requiring deep reasoning:
1. Use `ultrathink` for enhanced thinking 1. Ensure extended thinking is enabled (on by default)
2. Enable **Plan Mode** for structured approach 2. Enable **Plan Mode** for structured approach
3. "Rev the engine" with multiple critique rounds 3. Use multiple critique rounds for thorough analysis
4. Use split role sub-agents for diverse analysis 4. Use split role sub-agents for diverse perspectives
## Build Troubleshooting ## Build Troubleshooting

15
rules/security.md → rules/common/security.md
View File

@@ -14,17 +14,10 @@ Before ANY commit:
## Secret Management ## Secret Management
```typescript - NEVER hardcode secrets in source code
// NEVER: Hardcoded secrets - ALWAYS use environment variables or a secret manager
const apiKey = "sk-proj-xxxxx" - Validate that required secrets are present at startup
- Rotate any secrets that may have been exposed
// ALWAYS: Environment variables
const apiKey = process.env.OPENAI_API_KEY
if (!apiKey) {
throw new Error('OPENAI_API_KEY not configured')
}
```
## Security Response Protocol ## Security Response Protocol

3
rules/testing.md → rules/common/testing.md
View File

@@ -5,7 +5,7 @@
Test Types (ALL required): Test Types (ALL required):
1. **Unit Tests** - Individual functions, utilities, components 1. **Unit Tests** - Individual functions, utilities, components
2. **Integration Tests** - API endpoints, database operations 2. **Integration Tests** - API endpoints, database operations
3. **E2E Tests** - Critical user flows (Playwright) 3. **E2E Tests** - Critical user flows (framework chosen per language)
## Test-Driven Development ## Test-Driven Development
@@ -27,4 +27,3 @@ MANDATORY workflow:
## Agent Support ## Agent Support
- **tdd-guide** - Use PROACTIVELY for new features, enforces write-tests-first - **tdd-guide** - Use PROACTIVELY for new features, enforces write-tests-first
- **e2e-runner** - Playwright E2E testing specialist

26
rules/golang/coding-style.md Normal file
View File

@@ -0,0 +1,26 @@
# Go Coding Style
> This file extends [common/coding-style.md](../common/coding-style.md) with Go specific content.
## Formatting
- **gofmt** and **goimports** are mandatory — no style debates
## Design Principles
- Accept interfaces, return structs
- Keep interfaces small (1-3 methods)
## Error Handling
Always wrap errors with context:
```go
if err != nil {
return fmt.Errorf("failed to create user: %w", err)
}
```
## Reference
See skill: `golang-patterns` for comprehensive Go idioms and patterns.

11
rules/golang/hooks.md Normal file
View File

@@ -0,0 +1,11 @@
# Go Hooks
> This file extends [common/hooks.md](../common/hooks.md) with Go specific content.
## PostToolUse Hooks
Configure in `~/.claude/settings.json`:
- **gofmt/goimports**: Auto-format `.go` files after edit
- **go vet**: Run static analysis after editing `.go` files
- **staticcheck**: Run extended static checks on modified packages

39
rules/golang/patterns.md Normal file
View File

@@ -0,0 +1,39 @@
# Go Patterns
> This file extends [common/patterns.md](../common/patterns.md) with Go specific content.
## Functional Options
```go
type Option func(*Server)
func WithPort(port int) Option {
return func(s *Server) { s.port = port }
}
func NewServer(opts ...Option) *Server {
s := &Server{port: 8080}
for _, opt := range opts {
opt(s)
}
return s
}
```
## Small Interfaces
Define interfaces where they are used, not where they are implemented.
## Dependency Injection
Use constructor functions to inject dependencies:
```go
func NewUserService(repo UserRepository, logger Logger) *UserService {
return &UserService{repo: repo, logger: logger}
}
```
## Reference
See skill: `golang-patterns` for comprehensive Go patterns including concurrency, error handling, and package organization.

28
rules/golang/security.md Normal file
View File

@@ -0,0 +1,28 @@
# Go Security
> This file extends [common/security.md](../common/security.md) with Go specific content.
## Secret Management
```go
apiKey := os.Getenv("OPENAI_API_KEY")
if apiKey == "" {
log.Fatal("OPENAI_API_KEY not configured")
}
```
## Security Scanning
- Use **gosec** for static security analysis:
```bash
gosec ./...
```
## Context & Timeouts
Always use `context.Context` for timeout control:
```go
ctx, cancel := context.WithTimeout(ctx, 5*time.Second)
defer cancel()
```

25
rules/golang/testing.md Normal file
View File

@@ -0,0 +1,25 @@
# Go Testing
> This file extends [common/testing.md](../common/testing.md) with Go specific content.
## Framework
Use the standard `go test` with **table-driven tests**.
## Race Detection
Always run with the `-race` flag:
```bash
go test -race ./...
```
## Coverage
```bash
go test -cover ./...
```
## Reference
See skill: `golang-testing` for detailed Go testing patterns and helpers.

37
rules/python/coding-style.md Normal file
View File

@@ -0,0 +1,37 @@
# Python Coding Style
> This file extends [common/coding-style.md](../common/coding-style.md) with Python specific content.
## Standards
- Follow **PEP 8** conventions
- Use **type annotations** on all function signatures
## Immutability
Prefer immutable data structures:
```python
from dataclasses import dataclass
@dataclass(frozen=True)
class User:
name: str
email: str
from typing import NamedTuple
class Point(NamedTuple):
x: float
y: float
```
## Formatting
- **black** for code formatting
- **isort** for import sorting
- **ruff** for linting
## Reference
See skill: `python-patterns` for comprehensive Python idioms and patterns.

14
rules/python/hooks.md Normal file
View File

@@ -0,0 +1,14 @@
# Python Hooks
> This file extends [common/hooks.md](../common/hooks.md) with Python specific content.
## PostToolUse Hooks
Configure in `~/.claude/settings.json`:
- **black/ruff**: Auto-format `.py` files after edit
- **mypy/pyright**: Run type checking after editing `.py` files
## Warnings
- Warn about `print()` statements in edited files (use `logging` module instead)

34
rules/python/patterns.md Normal file
View File

@@ -0,0 +1,34 @@
# Python Patterns
> This file extends [common/patterns.md](../common/patterns.md) with Python specific content.
## Protocol (Duck Typing)
```python
from typing import Protocol
class Repository(Protocol):
def find_by_id(self, id: str) -> dict | None: ...
def save(self, entity: dict) -> dict: ...
```
## Dataclasses as DTOs
```python
from dataclasses import dataclass
@dataclass
class CreateUserRequest:
name: str
email: str
age: int | None = None
```
## Context Managers & Generators
- Use context managers (`with` statement) for resource management
- Use generators for lazy evaluation and memory-efficient iteration
## Reference
See skill: `python-patterns` for comprehensive patterns including decorators, concurrency, and package organization.

25
rules/python/security.md Normal file
View File

@@ -0,0 +1,25 @@
# Python Security
> This file extends [common/security.md](../common/security.md) with Python specific content.
## Secret Management
```python
import os
from dotenv import load_dotenv
load_dotenv()
api_key = os.environ["OPENAI_API_KEY"] # Raises KeyError if missing
```
## Security Scanning
- Use **bandit** for static security analysis:
```bash
bandit -r src/
```
## Reference
See skill: `django-security` for Django-specific security guidelines (if applicable).

33
rules/python/testing.md Normal file
View File

@@ -0,0 +1,33 @@
# Python Testing
> This file extends [common/testing.md](../common/testing.md) with Python specific content.
## Framework
Use **pytest** as the testing framework.
## Coverage
```bash
pytest --cov=src --cov-report=term-missing
```
## Test Organization
Use `pytest.mark` for test categorization:
```python
import pytest
@pytest.mark.unit
def test_calculate_total():
...
@pytest.mark.integration
def test_database_connection():
...
```
## Reference
See skill: `python-testing` for detailed pytest patterns and fixtures.

58
rules/typescript/coding-style.md Normal file
View File

@@ -0,0 +1,58 @@
# TypeScript/JavaScript Coding Style
> This file extends [common/coding-style.md](../common/coding-style.md) with TypeScript/JavaScript specific content.
## Immutability
Use spread operator for immutable updates:
```typescript
// WRONG: Mutation
function updateUser(user, name) {
user.name = name // MUTATION!
return user
}
// CORRECT: Immutability
function updateUser(user, name) {
return {
...user,
name
}
}
```
## Error Handling
Use async/await with try-catch:
```typescript
try {
const result = await riskyOperation()
return result
} catch (error) {
console.error('Operation failed:', error)
throw new Error('Detailed user-friendly message')
}
```
## Input Validation
Use Zod for schema-based validation:
```typescript
import { z } from 'zod'
const schema = z.object({
email: z.string().email(),
age: z.number().int().min(0).max(150)
})
const validated = schema.parse(input)
```
## Console.log
- No `console.log` statements in production code
- Use proper logging libraries instead
- See hooks for automatic detection

15
rules/typescript/hooks.md Normal file
View File

@@ -0,0 +1,15 @@
# TypeScript/JavaScript Hooks
> This file extends [common/hooks.md](../common/hooks.md) with TypeScript/JavaScript specific content.
## PostToolUse Hooks
Configure in `~/.claude/settings.json`:
- **Prettier**: Auto-format JS/TS files after edit
- **TypeScript check**: Run `tsc` after editing `.ts`/`.tsx` files
- **console.log warning**: Warn about `console.log` in edited files
## Stop Hooks
- **console.log audit**: Check all modified files for `console.log` before session ends

16
rules/patterns.md → rules/typescript/patterns.md
View File

@@ -1,4 +1,6 @@
# Common Patterns # TypeScript/JavaScript Patterns
> This file extends [common/patterns.md](../common/patterns.md) with TypeScript/JavaScript specific content.
## API Response Format ## API Response Format
@@ -41,15 +43,3 @@ interface Repository<T> {
delete(id: string): Promise<void> delete(id: string): Promise<void>
} }
``` ```
## Skeleton Projects
When implementing new functionality:
1. Search for battle-tested skeleton projects
2. Use parallel agents to evaluate options:
- Security assessment
- Extensibility analysis
- Relevance scoring
- Implementation planning
3. Clone best match as foundation
4. Iterate within proven structure

21
rules/typescript/security.md Normal file
View File

@@ -0,0 +1,21 @@
# TypeScript/JavaScript Security
> This file extends [common/security.md](../common/security.md) with TypeScript/JavaScript specific content.
## Secret Management
```typescript
// NEVER: Hardcoded secrets
const apiKey = "sk-proj-xxxxx"
// ALWAYS: Environment variables
const apiKey = process.env.OPENAI_API_KEY
if (!apiKey) {
throw new Error('OPENAI_API_KEY not configured')
}
```
## Agent Support
- Use **security-reviewer** skill for comprehensive security audits

11
rules/typescript/testing.md Normal file
View File

@@ -0,0 +1,11 @@
# TypeScript/JavaScript Testing
> This file extends [common/testing.md](../common/testing.md) with TypeScript/JavaScript specific content.
## E2E Testing
Use **Playwright** as the E2E testing framework for critical user flows.
## Agent Support
- **e2e-runner** - Playwright E2E testing specialist