skills.rest
yusifeng
yusifengCOMMUNITY
Explore all skills by this author →
GitHub

formax-script-output-placement-workflow

Route script-generated artifacts into owner directories instead of docs.

192|7|Updated Dec 30, 2025
Search Tags:#workflow#docs#scripts#ci#placement#artifact-management
One-click install
npx skills add https://github.com/yusifeng/formax --skill formax-script-output-placement-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: formax-script-output-placement-workflow
Source: https://github.com/yusifeng/formax/tree/main/.codex/skills/formax-script-output-placement-workflow
Command: npx skills add https://github.com/yusifeng/formax --skill formax-script-output-placement-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Keeps generated artifacts out of docs/ by ensuring machine outputs are placed under owner directories, preserving docs for documentation only.

Core Features & Use Cases

  • Placement rules enforce that docs/ contains only documents and static materials, while artifacts are stored under owner dirs (e.g., apps/<name>/perf/ for app artifacts, scripts/baselines/ for repo script outputs, and .tmp/ for temporary results).
  • Default output alignment ensures generated scripts point to an owner directory by default, with options like --output or --baseline to override for CI or local testing.
  • CI-friendly workflow updates are supported to keep baselines in sync with repository ownership and project structure.

Quick Start

Configure the default output path to an owner directory and run the script to place artifacts outside docs/.

Frequently Asked Questions about formax-script-output-placement-workflow

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

FAQPage Schema
How do I keep generated script artifacts out of my docs directory?▼

Route machine-generated artifacts into owner directories to keep docs clean. This workflow enforces placement rules so docs/ contains only documentation, while artifacts go to designated owner dirs like apps/<name>/perf/.

What is the best way to manage CI workflow artifacts and local script outputs?▼

Configure default output paths using options like --output or --baseline to align generated files with repository ownership rules. This keeps baselines synced across CI workflows and local development environments.

Where should temporary script outputs be placed in a repository?▼

Place temporary script outputs in the .tmp/ directory. This workflow ensures temporary results are isolated from documentation and organized under owner directories rather than cluttering the docs/ folder.

Can I override default artifact placement paths for local testing?▼

Override default artifact placement paths for local testing using options like --output or --baseline. Scripts default to owner directories but support redirection to align with CI rules or local development needs.

Why are my script-generated files polluting the docs folder?▼

Script-generated files pollute the docs folder when default output paths lack owner directory configuration. Applying artifact-management placement rules redirects these machine outputs to appropriate locations like scripts/baselines/.

Related Skills

Explore More Software Engineering Skills→
loianeloiane
50

brownfield-onboarding

Onboard an existing Spring codebase into a spec-driven workflow with baseline and design doc.

Community
Advanced
ConsiliencyConsiliency
8

post-impl-docs

Update README.md, CHANGELOG.md, docs/, and docstrings after code changes.

Official
Basic
AINative-StudioAINative-Studio

file-placement

Validate Markdown and shell script placement against repository directory conventions.

Official
Intermediate
csuzngjhcsuzngjh
1

inject-rule

Appends user-provided rule arguments to the Ad-hoc Rules section of USER_CONTEXT.md.

Community
Basic