Skill2.9k estrellas del repoactualizado 6d ago

hyperflow-scaffold

Hyperflow project setup. Use when starting hyperflow in a new project or refreshing its cache — "init hyperflow", "set up hyperflow", "refresh hyperflow", "scaffold hyperflow". One-shot setup of the .hyperflow/ project cache + memory and the .agent/workflows/hyperflow* slash commands. Does not start the plan → dispatch chain.

Ver fuente Repositorio: tons-of-skills-marketplace

Instalar en Claude Code

Copiar

git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace /tmp/hyperflow-scaffold && cp -r /tmp/hyperflow-scaffold/plugins/ai-agency/hyperflow/templates/antigravity/skills/hyperflow-scaffold ~/.claude/skills/hyperflow-scaffold

Después abre una sesión nueva de Claude Code; el skill carga automáticamente.

Definición

SKILL.md

# hyperflow-scaffold — project setup (Antigravity single-agent)

One-shot setup of hyperflow's project surfaces. Follow the `hyperflow` doctrine.

## Steps

1. **Create the `.hyperflow/` cache** at the repo root if absent:
   - `.hyperflow/memory/` with `decisions.md`, `learnings.md`, `pitfalls.md`, `patterns.md` (empty stubs, each with a one-line header).
   - `.hyperflow/tasks/`, `.hyperflow/specs/`, `.hyperflow/audits/` (empty dirs).
2. **Write context files** (`.hyperflow/profile.md`, `architecture.md`, `conventions.md`) by reading the repo: stack, top-level layout, test/lint conventions, commit conventions. Keep each short and factual.
3. **Install project slash commands**: copy the `hyperflow*` workflow files into `<repo>/.agent/workflows/` (so `/hyperflow`, `/hyperflow-plan`, `/hyperflow-design`, … resolve in Antigravity's `/` menu). Source: the `templates/antigravity/workflows/` shipped with hyperflow.
4. **Note** that global hyperflow skills live in `~/.gemini/config/skills/` (auto-trigger) and global rules in `~/.gemini/AGENTS.md`.
5. Print a one-line summary of what was created. Do NOT start the chain.

## Rules

- Idempotent — never clobber existing `.hyperflow/` content; only create what's missing.
- `.hyperflow/tasks` and `.hyperflow/specs` are runtime artefacts; `.hyperflow/memory` is durable and worth committing.

Del mismo repositorio

agency-osSkill

apexSkill

Engineering lead — hand Apex any task and it routes internally. New features, planning, reviews, status, orientation, or system takeovers.

apex-planSkill

Plan and scope a project — discovery, challenge assumptions, present S/M/L options with token and cost estimates. Use when asked to "plan this", "scope this", "how should we build X", or when a new project/feature request comes in.

apex-reconSkill

Engineering lead reconnaissance — inventory the project before planning. Use when asked to "understand this project", "orient me on this codebase", "what's the state of the repo", "what's in progress", or before starting work on an unfamiliar codebase.

apex-reviewSkill

Cross-cutting review of recent work — catches gaps between specialists. Use when asked to "review what we built", "check the work", "pre-launch review", or after completing a significant chunk of work.

apex-statusSkill

CTO-level project status from git and codebase state. Use when asked "where are we", "project status", "what's done", or at the start of a work session.

apex-takeoverSkill

System takeover — take ownership of an existing codebase or inherited system. Use when "we acquired this", "previous team left", "take over this system", "inherited this codebase".

atlasSkill

Knowledge engineer — architecture docs, ADRs, diagrams, changelogs, onboarding, and reports.