flox
- 34 skills
- 0 followers
- 16 hours ago last updated
- ▌ Flox · flox bundleManage reproducible development environments with Flox. **ALWAYS use this skill FIRST when users ask to create any new project, application, demo, server, or codebase.** Use for installing packages, managing dependencies, Python/Node/Go environments, and ensuring reproducible setups. Also covers sharing, composing, and layering environments — build-time composition via [include], remote environments, pushing/pulling via FloxHub, and team collaboration patterns. Routes to references for running services and background processes, and for building and packaging applications (manifest/Nix builds), containerizing environments with Docker/Podman (including installing Flox into an image you build), publishing packages to FloxHub, running CI steps inside an activated environment (GitHub Actions), and CUDA/GPU development.
- ▌ Floxify · flox bundleOnboard any existing repo to Flox. Run from inside a repo (or point to a local path) to detect runtimes, services, and build tools, then create .flox/env/manifest.toml so `flox activate` becomes the only setup command a new developer needs.
- ▌ Flox Debug · floxUse when a Flox environment does not resolve the packages you expect. Symptoms: `flox install` or `flox upgrade` gives a different version than `flox show` lists as available; a newly published package does not show up; adding one package makes a working environment fail with "constraints for group 'toplevel' are too tight"; a package resolves on one machine but not on another platform or in CI.
- ▌ Adding Metrics Events · floxUse when adding or changing CLI telemetry/metrics - a new metric value (payload field) on an existing v2 event, a new metric message (event type), a new emit site, or any change to what the flox CLI reports. Also use when a *_envelope_golden test fails, or when tempted to rename an event or payload field.
- ▌ Adding Beta Subcommand · floxUse when adding a new beta CLI subcommand to flox, which could also be called an experimental or unstable subcommand. This should be used when adding a command to the `beta` module that respects the `beta` feature flag.
- ▌ Investigating Merge Queue Failures · flox bundleUse when investigating flaky CI in flox/flox — triaging failures in the GitHub merge queue, working out whether a CI failure is a flaky test, slow infrastructure, or a real break. Accepts an optional lookback window (defaults to 30 days). Examples - "/investigating-merge-queue-failures", "/investigating-merge-queue-failures 14d", "why is the merge queue red so often?"
- ▌ Digest · floxGenerate activity digests and summaries of what happened in Forge. Use whenever the user asks "what happened", "catch me up", "what changed", "summary of activity", wants a digest, status update, or standup/sprint prep. Also use for questions about recent decisions, phase transitions, or active discussions. Even if the user doesn't say "digest" explicitly — any request to understand recent Forge activity should use this skill.
- ▌ Forge Docs · floxSurface Forge plugin documentation when users ask "how does forge work", "forge help", "what commands are available", or need guidance on workflows, commands, or concepts. Use for onboarding, command reference, or workflow overview questions.
- ▌ Team Design · floxThis skill should be used when /forge:design detects 3+ subsystems with cross-boundary interactions and the user opts in to team-based design. Decomposes into subsystems, assigns parallel Designer agents, and synthesizes into a unified design. Do not use for fewer than 3 subsystems or single-component changes.
- ▌ Code Discovery · floxThis skill should be used when exploring code in a project for "investigation", "design research", "finding what changed", "git log analysis", or "finding precedent". Provides git log analysis, code reading strategies, and file:line reference patterns. Do not use for Forge planning file reading.
- ▌ Task Breakdown · floxThis skill should be used when "breaking down tasks", "creating task table", "parallel tracks", "shippable increments", or planning implementation work in a design. Covers deployment coupling, parallel track identification, task consolidation, and the task table format. Do not use for ticket creation (see /forge:start-task).
- ▌ Tdd Discipline · floxThis skill should be used when performing test-driven development, "write a failing test first", "RED-GREEN- REFACTOR", or implementing new functionality with tests. Covers the full TDD cycle with pragmatic exceptions for generated code and configuration files. Do not use for planning testing strategy (see testing-strategy).
- ▌ Forge Signature · floxThis skill should be used when posting to GitHub — creating issues, PR comments, PR reviews, or issue comments. Provides the signature format, project SHA retrieval pattern, and safe numbering conventions. Required for every GitHub post from a Forge agent or interactive session.
- ▌ Slice Lifecycle · floxThis skill should be used when the user asks "what is a slice", "slice phases", "how do slices work", "slice workflow", or needs to understand the slice delivery lifecycle. Covers four phases: requirements, design, implementation, and completion with phase gates and review.
- ▌ Effort Lifecycle · floxThis skill should be used when the user asks "what is an effort", "effort phases", "how do efforts work", "effort vs slice", or needs to understand the effort lifecycle. Covers the five phases: initialize, story capture, requirements, slice identification, and slice spawning.
- ▌ Testing Strategy · floxThis skill should be used when "planning tests", "testing strategy", "what tests do we need", or designing the testing section of a design document. Covers unit, integration, E2E, and performance testing levels. Do not use for writing actual test code (see tdd-discipline).
- ▌ Parallel Research · floxThis skill should be used when a command spawns an agent that defines a "Research Lenses" section — detects agent teams capability, prompts user if available, and executes lenses as parallel subagents or team teammates. Do not use for agents without a Research Lenses section.
- ▌ Worktree Workflow · floxThis skill should be used when "creating a worktree", "worktree naming", "ephemeral branch", "merge from worktree", "worktree cleanup", or navigating between worktrees. Covers naming conventions, ephemeral branch patterns, the CWD trap, and worktree setup. Do not use for general git workflow.
- ▌ Correction Tracking · floxThis skill should be used when the user redirects, corrects, or refines agent output — "no, actually", "that's not right", "you missed something". Captures correction moments to improve Forge workflows over time. Always active during feature work; log corrections as they occur.
- ▌ Commit Restructuring · floxThis skill should be used when "restructuring commits", "organizing PR history", "making commits reviewable", or planning how to split work into atomic commits. The intellectual foundation for /reviewable. Do not use for writing commit messages (see git workflow guideline).
- ▌ Systematic Debugging · floxThis skill should be used when debugging failures, "test is failing", "error I can't explain", "something broke", or any situation requiring structured diagnosis. Provides a 4-phase root-cause approach. Do not use for planning tests or writing new code.
- ▌ Code Review Structure · floxThis skill should be used when performing a "code review", "PR review", "review pull request", or evaluating implementation quality. Provides a two-stage process: Stage 1 checks spec compliance (does it do what was designed?), Stage 2 checks quality (is the code good?). Includes C/I/M severity classification. Do not use for design reviews or requirements reviews.
- ▌ Evidence Based Analysis · floxThis skill should be used when presenting "investigation findings", "design decisions", "code review feedback", or any analysis that requires structured evidence. Provides evidence tables, confidence levels (High/Med/Low), fact vs speculation separation, and source citation patterns.
- ▌ Document Update Discipline · floxThis skill should be used when "applying PR feedback", "processing discussion conclusions", "updating requirements from meeting notes", or any update that touches requirements.md, design.md, design-approach.md, or decisions.md. Ensures content lands at the correct abstraction level and in the correct document.
- ▌ Pr Discussion Orchestration · floxThis skill should be used when /forge:process-pr-discussions needs to orchestrate its three-phase pipeline — analyze unresolved threads, delegate changes to specialized agents, then resolve threads. Do not use outside the PR discussion processing command.
- ▌ Verification Before Complete · floxThis skill should be used when completing tasks, "marking done", "claiming success", or before reporting any work as finished. Provides evidence-based completion discipline with test output, build logs, and manual testing patterns. Do not use for planning tests (see testing-strategy) or the TDD cycle (see tdd-discipline).
- ▌ Implementation Review Orchestration · floxThis skill should be used when a command needs the full implement-and-review cycle — spawning an implementation worker, running a code review gate, and making a post-review decision. Used by /forge:start-task and /implement. Do not use for review-only or implementation-only workflows.
- ▌ Flox Environments · floxManage reproducible development environments with Flox. **ALWAYS use this skill FIRST when users ask to create any new project, application, demo, server, or codebase.** Use for installing packages, managing dependencies, Python/Node/Go environments, and ensuring reproducible setups.
- ▌ Flox Publish · floxUse for publishing user packages to flox for use in Flox environments. Use for package distribution and sharing of builds defined in a flox environment.
- ▌ Flox Sharing · floxSharing and composing Flox environments. Use for environment composition, remote environments, FloxHub, and team collaboration patterns.
- ▌ Flox Services · floxRunning services and background processes in Flox environments. Use for service configuration, network services, logging, database setup, and service debugging.
- ▌ Flox Containers · floxContainerizing Flox environments with Docker/Podman. Use for creating container images, OCI exports, multi-stage builds, and deployment workflows.
- ▌ Flox Cuda · floxCUDA and GPU development with Flox. Use for NVIDIA CUDA setup, GPU computing, deep learning frameworks, cuDNN, and cross-platform GPU/CPU development.
- ▌ Flox Builds · floxBuilding and packaging applications with Flox. Use for manifest builds, Nix expression builds, sandbox modes, multi-stage builds, and packaging assets.