AI Skill Report Card
Converting Craft Patterns to Logic Blocks
Quick Start15 / 15
Input (raw pattern excerpt):
Magic ring, 6 sc. Then work 2 sc in each st around (12). Next round,
*1 sc, 2 sc in next* around (18). Work even for 3 rounds. Then *4 sc,
dec 1* around (15)... decrease down to 6, fasten off.
Output:
Recommendation▾
Add a second worked example covering a chart-based craft (cross-stitch/beadwork) to demonstrate the ASCII matrix output referenced in the rules, since currently only the crochet numeric case is shown
PREREQUISITES
- Base Unit: Magic Ring
- Medium Ratio: FLAG: UNDECLARED
- Gauge/Tension: FLAG: UNDECLARED
- Boundary Metric: FLAG: UNDECLARED
MODULE 1: FOUNDATION PRIMITIVES
R1: (sc) x6 [6]
MODULE 2: VOLUMETRIC EXPANSION
R2: (2 sc in each st) x6 [12] R3: (sc, 2 sc) x6 [18]
MODULE 3: DIMENSIONAL STABILIZATION
R4-R6: (sc) x18 [18] (x3 rows)
MODULE 4: CONTRACTION CLOSURE
R7: (4 sc, dec 1) x3 [15] R8: (dec 1) x[N] [6]
EXCEPTION ROUTING LABS
- IF [Active Count] != 18 AT R3: RUN Recount Routine -> Redeposit deltas evenly across R2.
- IF [Active Count] != 15 AT R7: RUN Compensation Loop -> Pad/decrease local stitches before R8.
Workflow14 / 15
Progress:
- Gate 1: Ingest & Isolate — strip prose, extract raw numeric/directional tokens
- Gate 2: Validate environmental variables (Base Anchor, Medium Ratio, Gauge, Thickness) — flag anything undeclared
- Gate 3: Decompose into exactly 4 nodes (Foundation, Expansion, Stabilization, Closure) with running stitch-count checkpoints
[N]on every row - Gate 4: Inject IF/THEN exception routing at expansion-end and contraction-start boundaries
- Render final output using the fixed blueprint — no preamble, no postscript
Never skip a gate. If Gate 2 data is missing, still proceed through Gates 3-4, but every prerequisite field without a source value gets FLAG: UNDECLARED — do not invent a plausible default (no assuming "4mm hook" or "worsted weight" if not stated).
Recommendation▾
Include a 'bad output' contrast example (e.g., a narrative-style conversion that violates the rules) to make the good/bad distinction concrete rather than only describing pitfalls in prose
Node Rules (Gate 3)
- Foundation Primitives: opening anchor + initial stitch count only. One row line, ends in
[N]. - Volumetric Expansion: every increase row as
(Formula) xMultiplier [N]. Each distinct increase row gets its own line — do not collapse expansion rows even if formulas repeat, unless the source explicitly states "repeat rounds X-Y identically." - Dimensional Stabilization: collapse any run of ≥2 consecutive rows with identical stitch formula and identical count into one ranged line:
R[start]-R[end]: [Formula] [N] (x[count] rows). - Contraction Closure: strictly decreasing counts, terminating in an explicit final value (cinch, fasten off, bind off). Last line must state the terminal count, never "0" unless the pattern truly closes to zero.
Formula Syntax
- Use
(Action, Action) xN [Total]— parentheses wrap the repeating unit,xNis repeat multiplier,[Total]is the resulting running stitch count. - Never use sentences like "increase in every other stitch." Convert to
(sc, 2 sc in next) xN [N]. - Grid/chart patterns (cross-stitch, beadwork): render as ASCII matrix (rows/columns of symbols) + one formula descriptor line beneath. Never narrate the visual.
- Max 5 lines per module block for mobile viewport constraint. If a module exceeds 5 lines, split into sub-blocks labeled
MODULE Na,MODULE Nb.
Exception Routing (Gate 4)
Always emit exactly two conditional checks minimum:
- One
IF/THENimmediately after the last Expansion row (validates count before Stabilization begins). - One
IF/THENimmediately before the first Contraction row (validates count before decreases begin).
Format strictly as:
IF [Active Count] != [Target Count] AT R[label]: RUN [Recount Routine|Compensation Loop] -> [corrective action]
Best Practices
- Treat every row as a state transition: input count → operation → output count. If the source pattern doesn't make the math work, flag it in Exception Routing rather than silently correcting it.
- When medium/gauge data is genuinely absent, propagate
FLAG: UNDECLAREDinto PREREQUISITES verbatim — this is a signal to the human, not an error to hide. - For amigurumi/3D nets: track running total as a single integer per row. For flat charts (cross-stitch/beadwork): track as (row, column) grid coordinates instead, still using ASCII matrix output.
- Keep output 100% mechanical — no encouragement, no design commentary, no "you're doing great."
Common Pitfalls
- Do not assume a default hook size, gauge, or yarn weight when undeclared — always flag instead of guessing.
- Do not collapse Expansion rows into ranges even if they look similar — only Stabilization rows collapse.
- Do not output conversational transitions ("Now let's look at...") between modules — modules are separated only by headers.
- Do not omit the terminal count in Contraction Closure — every pattern must resolve to an explicit final state.
- Do not merge Exception Routing into the row modules — it is always a separate trailing section.