seniordev

Enforces minimal code solutions by prioritizing stdlib, native features, and YAGNI principles.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/kellymears/agents --skill seniordev-kellymears
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: seniordev
Source: https://github.com/kellymears/agents/tree/main/plugins/seniordev/skills/seniordev
Command: npx skills add https://github.com/kellymears/agents --skill seniordev-kellymears

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Codebases accumulate over-engineered abstractions, unnecessary dependencies, and speculative features that create maintenance burden. This Skill forces the simplest working solution by applying a senior developer's judgment: question whether code needs to exist, prefer the standard library, and ship the shortest working diff. ## Core Features & Use Cases - The Ladder: A decision hierarchy that stops at the first working rung — YAGNI check, stdlib, native platform features, existing dependencies, one-liners, then minimal code. - Intensity Levels: Three modes (lite, full, ultra) control how aggressively simplification is enforced, switchable with /seniordev lite|full|ultra. - Deliberate Simplification Markers: seniordev: comments document intentional shortcuts with their known ceilings and upgrade paths. - Use Case: When asked to add a caching layer for API responses, instead of building a custom cache class, the Skill applies @lru_cache(maxsize=1000) and notes when a custom solution would actually be needed. ## Quick Start Ask the assistant to use seniordev mode to implement your next feature with the simplest solution that works.

Frequently Asked Questions about seniordev

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I avoid over-engineering code with AI assistance?▼

Activate seniordev mode, which applies a decision ladder: check if the code needs to exist, prefer stdlib and native platform features, use existing dependencies, then write the minimum code that works. It ships the shortest working diff instead of speculative abstractions.

What are the seniordev intensity levels lite, full, and ultra?▼

Lite builds what is asked but names a lazier alternative. Full (the default) enforces the ladder with stdlib-first solutions and the shortest diff. Ultra is YAGNI-extremist, preferring deletion over addition and challenging requirements directly.

When should I not use a minimal-code approach?▼

Never simplify away input validation at trust boundaries, error handling that prevents data loss, security measures, accessibility basics, or anything explicitly requested. Non-trivial logic should also leave one small runnable check behind.

How do I turn off seniordev mode or switch levels?▼

Say "stop seniordev" or "normal mode" to revert to standard behavior. Switch intensity at any time with /seniordev lite, /seniordev full, or /seniordev ultra; the level persists until changed or the session ends.

Does minimal code mean skipping tests entirely?▼

No. Non-trivial logic such as branches, loops, parsers, or money and security paths gets one small runnable check, like an assert-based self-check or a single test file. Trivial one-liners need no test, and no frameworks are added unless asked.