Skip to content

moonlight-lupin/agent-skills / plugins/dev-pipeline/skills/spec

Use when pinning intent before code — capture a spec (user stories, acceptance criteria, [NEEDS CLARIFICATION] markers), then plan the HOW (bite-sized tasks, blocking edges, gates) or slice tracer-bullet tickets. Triggers: 'write a spec', 'plan this', 'break this into tickets', 'slice this up', 'create tickets', 'what are the work units'.

references/goldfish/standards/zoom-out-standard.md

View on GitHub
# Zoom Out Standard

This standard defines the quality bar for evaluating high-level designs,
architectures, and implementation plans from a high-altitude perspective.

## Core Principle

A design passes if it solves the root problem in the simplest possible way,
leverages existing infrastructure and codebase conventions, avoids premature
optimization or speculative features (YAGNI), and maintains appropriate
abstraction boundaries without getting bogged down in low-level code
implementation details.

## 0. Context Sufficiency (Prerequisite Check)

*   **Understanding the Objective**: The document must contain enough
    information to define the overall objective. If the reviewer cannot
    determine *what* we are trying to achieve and *why*, the review must fail
    immediately with a request for context.

## 1. Root Problem Focus

*   **Symptom vs. Root Cause**: The design must solve the underlying problem,
    not just apply a local band-aid to symptoms.
*   **Project Alignment**: The design must align with the high-level goals and
    architectural philosophy defined in the project's root documentation
    (`README.md` or `context.md`).

## 2. Simplicity & Extensibility

*   **YAGNI (You Aren't Gonna Need It)**: Reject abstractions, code paths, or
    features built solely for speculative future requirements.
*   **Premature Optimization**: Avoid introducing complexity (caching, sharding,
    async queues) before performance bottlenecks are proven.
*   **Minimalist Data Flow**: Ensure data passes through the minimal number of
    components.
*   **No Architectural Dead-Ends**: Use clean interfaces and boundaries to allow
    future expansion without blocking it, without implementing speculative
    features now.

## 3. Anti-Weeds (Altitude Control)

*   **Premature Detail**: High-level sections must focus on architecture,
    interfaces, and data flows, not code-level implementation details (e.g.,
    helper functions or loop variables).
*   **Workarounds vs. Structural Fixes**: Avoid complex local workarounds;
    propose changes to the root component if that is cleaner.
*   **Right Placement (Architectural Fit)**: Ensure new logic is placed in the
    correct layer/component according to separation of concerns.

## 4. Leverage Existing

*   **Codebase Reuse**: Search the codebase and reuse existing utilities,
    classes, or modules instead of reinventing them. Ensure the candidate for
    reuse is stable, maintained, and does not violate dependency boundaries.
*   **Pattern Consistency**: Follow established design patterns in the codebase.
*   **Platform Standards**: Use established ecosystem frameworks and standard libraries
    instead of bespoke or ad-hoc custom solutions.
*   **Identify Anti-Patterns**: Actively flag known anti-patterns
    (e.g., bypassing standard authentication, hardcoding deployment configurations).
planning-and-task-breakdownaddyosmani/agent-skillsBreaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
screenpipethedotmack/claude-memSearch screen and audio history recorded by Screenpipe and optionally save selected context into claude-mem. Use when the user asks to recall desktop activity, a meeting, or something seen in another app through Screenpipe.Stars: 118kUpdated Claude CodeCodexVerifiedInstall
contact-widgetnexu-io/open-designSelf-contained floating chat widget with welcome screen, social links, meeting button, and message input. Single HTML file, zero dependencies.Stars: 108kUpdated Claude CodeCodexVerifiedInstall
meeting-notesnexu-io/open-designMeeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".Stars: 108kUpdated Claude CodeCodexVerifiedInstall