Design Motion Principles
Choose motion from the task: feedback, continuity, or orientation; specify interruption and reduced-motion behavior.
Turn a process into a readable mechanical diagram: identify inputs, transformations, and outputs before choosing geometry.
---
name: knoveya-anatomy
description: "Turn a process into a readable mechanical diagram: identify inputs, transformations, and outputs before choosing geometry. Use for matching visual design work."
---
# Anatomy
## Scope
Apply this guidance when the requested task matches the description. Honor the user's chosen outcome, repository rules, and existing authorization.
## Workflow
Turn a process into a readable mechanical diagram: identify inputs, transformations, and outputs before choosing geometry.
Before acting, inspect the relevant artifact and ask only for information that materially changes the result. Use existing tools and conventions; do not install dependencies, publish, send messages, deploy, or mutate external data unless the user has authorized that operation.
## Acceptance check
Every moving part represents an actual state change, with a static equivalent.
## Example task
Explain an order-routing process with labelled gates rather than decorative gears.
## Report
State what changed, the evidence checked, and what remains unverified. Do not claim a successful operation or completed test without observing it.Copy the full block, including its frontmatter, into a new folder named knoveya-anatomy as SKILL.md. Review the instructions before enabling them. For Codex, a user skill normally lives in ~/.codex/skills/knoveya-anatomy/SKILL.md; check the current documentation for another agent's supported location. Do not overwrite an existing skill.
This is an independent Knoveya skill. No files are installed by this website.
Explain an order-routing process with labelled gates rather than decorative gears.
Every moving part represents an actual state change, with a static equivalent.
Test the skill on a small, authorized example. File validation alone does not prove that an agent will make good decisions.
The skill supplies instructions, not tool access or expertise guarantees. Inspect generated work and preserve the user's approval boundaries.