Claude Skills by Andersseen

Request independent review after meaningful implementation.

Evolve a live schema without downtime or data loss.

Keep credentials out of source, logs and client bundles.

Apply input validation, output encoding and least privilege by default.

Use native elements and structure so accessibility works by default.

Emit machine-readable logs with the context needed to diagnose incidents.

Coordinate scoped subagent work when the current provider supports it.

Find the root cause from evidence instead of guessing at fixes.

Explore codebases through search, relevant ranges, and module ownership.

Write documentation that answers the reader's question quickly.

Use fakes, stubs and mocks deliberately instead of mocking everything.

Choose the right test level and scope before writing tests.

Choose transaction boundaries and handle concurrent writes correctly.

Model TypeScript domains with unions, readonly data, satisfies, and useful generics.

Use current TypeScript module, syntax, import, and async patterns.

Use TypeScript strictness, narrowing, and validation for safe boundaries.

Back completion claims with evidence, and report failures plainly.

Optimize loading, interactivity and layout stability for real users.

Use git worktrees for isolated parallel implementation when the work warrants it.