fft-coder-ops
- Repo stars 0
- Author updated Live
- Author repo nano-core
- Domain
- Engineering
- Compatible agents
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- Trust score
- 88 / 100 · community maintained
- Author / version / license
- @0-CYBERDYNE-SYSTEMS-0 · no license declared
- Token usage
- Lean
- Setup complexity
- Guided setup
- External API key
- Not required
- Operating systems
- Unspecified (assume cross-platform)
- Runtime requirements
- No special requirements
- Permissions
-
- Read-only
- Shell exec
- Write / modify
- Network behavior
- Local-only
- Install commands
- 26 variants
Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.
Heads up: 未限定 allowed-tools，默认拥有全部工具权限。
---
name: fft-coder-ops
description: Operate FFT_nano coding delegation flows safely using /coder and /coder-plan, preserving main-ch…
category: engineering
runtime: no special runtime
---
# fft-coder-ops output preview
## PART A: Task fit
- Use case: Operate FFT_nano coding delegation flows safely using /coder and /coder-plan, preserving main-chat-only policy, request-id tracking, and non-duplicative streaming behavior. Use when enforcing main/admin chat boundaries for coding execution. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “When to use this skill / When not to use this skill / Guardrails” and do not present inference as author intent.
## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Operate FFT_nano coding delegation flows safely using /coder and /coder-plan, preserving main-chat-only policy, request-id tracking, and non-duplicative streaming behavior. Use when enforcing main/admin chat boundaries for coding execution. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “When to use this skill / When not to use this skill / Guardrails” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
## Running Rules
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options. Choose the trigger
The source mentions slash commands such as `/coder`, `/coder-plan`; use them first when your agent supports command triggers.
Provide inputs and boundaries
Name target files or source material, expected output, forbidden changes, and whether network or shell access is allowed. Permission fingerprint: read files, run shell commands, write/modify files.
Validate with a small run
Start with a small task and check whether the result follows “When to use this skill / When not to use this skill / Guardrails”. Inspect diffs, logs, previews, or tests before expanding scope.
Review before delivery
Confirm the final output includes a concrete result, evidence, and next action. If it stays generic, tighten inputs, boundaries, and acceptance criteria.
---
name: fft-coder-ops
description: Operate FFT_nano coding delegation flows safely using /coder and /coder-plan, preserving main-ch…
category: engineering
source: 0-CYBERDYNE-SYSTEMS-0/nano-core
---
# fft-coder-ops
## When to use
- Operate FFT_nano coding delegation flows safely using /coder and /coder-plan, preserving main-chat-only policy, reques…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.
## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.
## Execution rules
- Organize steps around “When to use this skill / When not to use this skill / Guardrails” and keep inference separate from source facts.
- read files, run shell commands, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.
## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies. Evidence boundary and execution chain
The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.
skill "fft-coder-ops" {
input -> user goal + target files + boundaries + acceptance criteria
context -> When to use this skill / When not to use this skill / Guardrails
rules -> SKILL.md triggers / order / output contract
runtime -> no special runtime | read files, run shell commands, write/modify files | mostly runs locally
guardrails -> usually needs no extra API key + small-sample validation + diff/log review
output -> copyable result + checklist + next iteration
}FFT Coder Ops
Use this skill when handling coding delegation operations in FFT_nano.
When to use this skill
- Use for
/coderand/coder-plandelegation workflows. - Use when enforcing main/admin chat boundaries for coding execution.
- Use when tracking delegated run IDs and progress-stream behavior.
When not to use this skill
- Do not use for non-coding tasks or normal chat replies.
- Do not use when no explicit delegation trigger is present.
- Do not use in non-main chats for delegated execution.
Guardrails
- Never run destructive git commands unless explicitly requested.
- Preserve unrelated worktree changes.
- Never bypass main-chat-only coder delegation safety rules.
- Do not add automatic delegation; delegation remains explicit trigger-based.
Delegation Triggers
Explicit execute:
/coder <task>use coding agentuse your coding agent skill
Explicit plan-only:
/coder-plan <task>
Natural-language coding requests without explicit trigger must not auto-delegate.
Chat Safety Rules
- Delegation is only available in main/admin chat.
- Non-main chats may request coding help, but must be handled directly or rejected for delegation.
- Scheduled tasks must not trigger coder delegation.
Runtime Expectations
- Execute mode delegates once and returns delegated outcome.
- Plan mode returns implementation/test plan without direct edits in outer orchestrator turn.
- Delegation run IDs are generated (
coder-<timestamp>-<suffix>) and surfaced in progress messages. - Progress streaming should avoid final duplicate full-message sends.
Operator Commands
Main Telegram chat commands:
/coder <task>/coder-plan <task>
Alias phrases in main chat:
use coding agentuse your coding agent skill
Validation Checklist
- Non-main
/coderis rejected with safety message. - Main
/codertriggers delegation run start message. - Main
/coder-plantriggers plan run start message. - Existing Telegram delegation safety rules remain unchanged.
Decide Fit First
Design Intent
How To Use It
Boundaries And Review