structural-pre-flight
byneomjs· 38 skills
Authoritative pre-implementation discipline gate that fires when a new .mjs file is about to be authored. Stage 0 mechanical trigger; Stage 1 fast-path (sibling-file-lift pattern match) for matched patterns OR full Pre-Flight (ArchitectureOverview.md + ADR consultation + chief-architect framing) for novel directory choices. Closes the 0th-level discipline gap empirically demonstrated by ai/daemons/wake/daemon.mjs (originally misplaced in ai/scripts/ as bridge-daemon.mjs) and orchestrator-daemon.mjs (PR #11008 same-class miss). Triggers: Use this skill before authoring or relocating any new .mjs file. Fires from ticket-create Stage 3 (Substrate), ticket-intake validation, epic-review Stage 3, and any direct authoring path. Sibling pattern match → 30-second fast-path; novel directory choice → full structural pre-flight before the file is written.
How to install structural-pre-flight?
neomjs/neo/structural-pre-flight
$npx -y skills add neomjs/neo --skill structural-pre-flightInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/neomjs/neo" --skill "neomjs/neo/structural-pre-flight"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/neomjs/neo" that are relevant to the current task. Run `npx skills add "https://github.com/neomjs/neo"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- improve-codebase-architectureScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.Jul 2026
- domain-modelingBuild and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision,…Jul 2026
- caveman-reviewUltra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix.Jul 2026
- codebase-designShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a…Jul 2026
- code-reviewReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes — Standards (does the code follow this repo's documented coding…Jul 2026
- resolving-merge-conflictsUse when you need to resolve an in-progress git merge/rebase conflict.Jul 2026
