Have the agent write code throughout the entire session following the principle of "solving the problem completely with the least amount of new code": first list the callers, tests, and configurations that must be affected by the changes, then select a solution based on the order of "does it need to exist → is there an existing one in the repository → standard library → installed dependencies → one line → minimal code", and at the end of the response, use one or two lines to explain what was skipped and what the risks are.
skills.sh installs 111808 (+1464 / 24h)
Security Audit: Not audited
- Not yet scanned
Rationale
- "Lazy" applies only to the solution, not the scope of changes: callers, tests, and fixtures broken by the changes must all be fixed; before fixing a bug, grep all callers and fix the root cause in shared code
- Explicitly non-omittable items: validation at trust boundaries, error handling to prevent data loss, security, accessibility, and user requirements; new non-trivial logic must include a small test or assertion for self-checking
- Shortcuts with known limitations should be written as comments in the format shortcut: <limitation>, <when to upgrade>; divided into three tiers: lite / full / ultra, where ultra questions the requirements themselves before starting work
- skills.sh installs 1464 in 24 hours, cumulative 111808 (represents attention level only)
Usage
- Activate by saying "ponytail", "be lazy", "simplest solution", "yagni", or complaining about over-engineering; switch tiers with /ponytail lite|full|ultra, deactivate by saying "stop ponytail" or "normal mode"
Risks
- Not audited this period, fixed at C-level, install command not displayed; the SKILL.md on GitHub contains only text rules, no scripts or network requests
- Trade-offs for the "minimal version" are judged by the agent; vague requirements may result in a minimal viable product, and necessary extensions must be specified in the prompt
- Similar in concept to caveman recorded yesterday: one manages response length, the other manages code volume; watch for rule conflicts when both are enabled simultaneously