sp coding agent

Design Community

Skill notes

How to Load This Skill

Set system prompt: Load references/system-prompt.md as the agent's system prompt (e.g., paste into AGENTS.md, .claude/system_prompt.md, or the agent's system role configuration). Provide reference files: Make references/logic.md, references/overlap-rules.md, and references/coding-agent-categories.md available in the agent's context or knowledge base. Invoke: Give the agent a vague or specific coding task. The agent will ORIENT (scan the codebase), CLASSIFY the task type, EXTRACT SP-categories, and check execution gates before touching any file.

Reference Files

File · Purpose references/system-prompt.md · 🔴 Required — Full Coding Agent system prompt (v4.0). Load as the agent's system instructions. references/logic.md · Framework logic: category definitions, weighted scoring, task-type classification, generic-to-coding task mapping. references/overlap-rules.md · Atom overlap rules, conflict detection, Functional Gravity principle, and the One Atom One Slot rule.

When to Use This Skill

A user gives a vague coding task ("fix the login bug", "add pagination") Before an agent starts multi-file code changes When a task involves unfamiliar parts of a codebase Migration or refactoring tasks where scope control is critical

How It Works

ORIENT: Agent scans project root (README.md, AGENTS.md, package.json, Dockerfile, etc.) CLASSIFY: Determine task type (Bug Fix / Feature / Refactor / Migration / Infra) EXTRACT: Map request to 9 code-native SP-categories DETECT FLAWS: Identify missing context, overlaps, and conflicts; ask user if critical PLAN: Create implementation plan with file-level scope

The 9 Code-Native Categories

Abbrev · Category · Code Meaning · Priority S · Style · Code standards, linting, architecture pattern · 🟢 Auto-detect M · Mastery · Developer expertise level — split into Domain vs Task (see below) · 🟡 Contextualizer A · Aim · Definition of Done, acceptance criteria, success metric · 🔴 CORE R · Resource · Allowed/forbidden deps, API quotas, team contacts, internal docs · 🟡 Contextualizer

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Moderate
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Python >=3.11 · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview sp-coding-agent.preview
# Worked Example: Bug Fix Context Extraction

**User request**: `"Fix the login bug — users can't login after password reset"` | SP-cat | Atom | Why here, not elsewhere | |--------|------|------------------------| | **S** | `Auto-detect from .eslintrc` | Style from project config | | **M-Domain** | `Senior Backend Developer` | Tech stack expertise | | **M-Task** | `Novice — unfamiliar with this legacy auth system` | Task-specific gap | | **A** | `Login succeeds with new password; old session invalidated; unit tests pass` | Success criteria → **not** T | | **R-Tools** | `Redis CLI access, Sentry error traces` | Concrete toolbox | | **R-Net

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.