planning

Design Community

Skill notes

What goes where

Item · Location · Why IC wrapper modules · packages/<name>/<name>.ato · Complex pin mapping, reusable All raw parts · parts/ (project root) · Installed by parts_install Simple self-contained parts · Used directly in main.ato · No supporting components or high-level interfaces needed (e.g. connectors, LEDs, test points) Generic passives · stdlib (import Resistor) · No package needed

Key rules

ICs always get wrapper packages — MCU, gate driver, transceiver, anything with complex pin mapping Wrapper modules expose standard interfaces — ElectricPower, I2C, SPI, CAN, UART, SWD, USB2_0, USB2_0_IF, ElectricLogic, ElectricSignal, not raw pins Check stdlib before defining new interfaces — if stdlib already has the right interface, or the boundary can be modeled as arrays/composition of stdlib interfaces, use that instead of inventing a project-local interface

Clean main.ato

The file at packages/<name>/<name>.ato is the canonical wrapper boundary for that part or subsystem. Refine that file in place. main.ato should import those wrapper packages directly rather than routing through an extra wrapper aggregator file. Requirements in Docstrings Capture natural-language requirements directly in the module's docstring under a Requirements: section. Place requirements on whichever module owns them — top-level for system-wide requirements, on a specific subsystem for module-specific ones.

How spec concepts map to ato

Spec Concept · ato Mechanism Overview · Module docstring ("""...""") Architecture · Sub-modules + connections (~) Requirements · - R<id>: <text> — <criteria> in module docstring Formal constraints · assert statements

Phase 1: Spec & Ask (end turn after this)

Do steps 1-5 in a SINGLE turn — do not end your turn after announcing you will plan. Read existing project files to understand current state.

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
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@atopile · MIT
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
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 planning.preview
# Phase 4: Report results

10. **Return results** with a concise summary of what changed, build status, and any assumptions you made.
- **Do not ask whether to plan** — for complex tasks, just do it. The user sees the spec and can steer.
- The spec IS the design file — same modules, same names, same structure. It just starts abstract and gets filled in.
- **Do not rename modules** when transitioning from spec to implementation. `PowerSupply` stays `PowerSupply`.
- Place requirements in the docstring of whichever module owns them, not all on the top-level.
- **IC wrappers go in `packages/`**, not in `main.ato`. Raw `_package` components are never imported in `main.ato`.

Discussion

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