shortcut

Enforce production-quality standards to prevent shortcuts in engineering work.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/fasterthanlime/_claude --skill shortcut-fasterthanlime
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: shortcut
Source: https://github.com/fasterthanlime/_claude/tree/main/skills/shortcut
Command: npx skills add https://github.com/fasterthanlime/_claude --skill shortcut-fasterthanlime

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill enforces engineering discipline to avoid shortcuts under pressure, ensuring tests, scope, and quality are preserved for long-term maintainability.

Core Features & Use Cases

  • No Shortcuts under Pressure: Do not disable tests or functionality; fix root causes instead.
  • No Placeholders or TODOs: Implement now or ask for clarification rather than shipping incomplete work.
  • Respectful Scope Management: Do not silently cut scope; present options or request explicit permission.

Quick Start

When under tight deadlines, respond with a clear plan to implement the full solution and, if needed, propose phased delivery with explicit scope choices.

Frequently Asked Questions about shortcut

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

FAQPage Schema
How do I avoid cutting corners when working under tight deadlines?

Avoid cutting corners by fixing root causes instead of disabling tests or reducing scope. Implement full solutions even under pressure, propose phased delivery with explicit scope choices if needed, and maintain production-quality standards throughout to ensure long-term maintainability.

Should I use TODOs and placeholders when I don't have time to finish something?

No. Instead of shipping incomplete work with TODOs or placeholders, implement the feature now or ask for clarification on scope and timeline. This prevents technical debt and ensures handoffs are complete and traceable for future maintainers.

What's the best way to handle scope changes during development?

Never silently cut scope. Present explicit options to stakeholders, request permission before reducing features, and document all scope decisions. This maintains transparency and prevents surprises in long-term code maintenance.

Why shouldn't I disable tests to meet a deadline?

Disabling tests masks real issues and creates maintenance risks over 10-20 years. Instead, identify and fix the root cause. Tests enforce production-quality standards and catch problems early, protecting code quality and team confidence.

How do I ensure comprehensive handoffs when context limits arise?

Document all decisions, implementation details, and scope rationale explicitly. Provide thorough traceability so the next person understands the work and constraints. Complete handoffs prevent knowledge loss and maintain code durability across team transitions.