AI Skill Report Card
Translating Craft Patterns to Logic
Translating Craft Patterns to Logic
Treats physical textile geometry as a bounded system of discrete states and mathematical rules — not an "artsy" narrative craft. Strips conversational fluff, isolates pure spatial/structural data, and outputs a clean, sellable pattern asset.
Quick Start15 / 15
Given a source (photo, existing pattern, or described shape), produce four sections in order:
- Asset Descriptor Deck — alphanumeric shorthand, layout grid or row ledger, color key
- Prerequisite State Manifest — materials, base stitch/loop counts, tension/gauge, hook/needle size
- Granular Workflow Decomposition — Foundation → Expansion → Stabilization → Contraction nodes
- Non-Linear Branching Exception Protocol — troubleshooting/adjustment loops
Example minimal output for a sphere-based amigurumi head:
MANIFEST
- Yarn: worsted, 4mm hook, 6 base ch
- Gauge: 12sc = 3in
- Stuffing: firm, poly-fil
FOUNDATION
R1: 6 sc in magic ring (6)
R2: inc x6 (12)
EXPANSION
R3: [sc, inc] x6 (18)
R4: [sc2, inc] x6 (24)
R5: [sc3, inc] x6 (30)
STABILIZATION
R6-R10: sc around, no shaping (30)
CONTRACTION
R11: [sc3, dec] x6 (24)
R12: [sc2, dec] x6 (18)
R13: [sc1, dec] x6 (12)
R14: dec x6 (6) → close, fasten off
EXCEPTION PROTOCOL
- If circumference deviates >0.5in at R5: adjust R6-10 count by ±2 rows before returning to Contraction.
- If tension loosens mid-round: drop 1 dec earlier in nearest Contraction row.
Recommendation▾
Add a third example covering a sewing/garment pattern (not just amigurumi and quilting) to show breadth across the stated domain
Workflow14 / 15
Progress:
- Parse source material into raw alphanumeric descriptors (no adjectives, no narrative)
- Build Asset Descriptor Deck (layout grid / row ledger / color key)
- Declare Prerequisite State Manifest (materials, base counts, tension, ply)
- Decompose into 4 workflow nodes (Foundation, Expansion, Stabilization, Contraction)
- Write Non-Linear Branching Exception Protocol for likely failure points
- Format each node as an independent, mobile-screen-sized block
- Package as Multi-Variant Listing Payload if output is a sellable asset
Node rules:
- Foundation: anchor loops, base stitch allocation, starting geometry only
- Expansion: rate of increase per row, compounding unit distribution
- Stabilization: constant-count rows, locks volumetric dimension
- Contraction: reduction sequence, closure math
- Each node stands alone — no cross-referencing prose, just numbers and stitch codes
Recommendation▾
Mention the 'Multi-Variant Listing Payload' packaging format concretely (e.g., what fields go into a sellable digital download) since it's referenced but never demonstrated
Examples17 / 20
Example 1: Input: "A basic amigurumi ball, worsted weight, 4mm hook" Output: Full 4-section breakdown (Manifest → Foundation R1-2 → Expansion R3-5 → Stabilization R6-10 → Contraction R11-14) with exception rules for gauge drift, as shown in Quick Start.
Example 2: Input: "Antique nine-patch quilt block, historical pattern photo" Output:
DESCRIPTOR DECK
Grid: 3x3 modular block, 9 unit squares, 2 alternating colorways (A/B)
Layout ASCII:
[A][B][A]
[B][A][B]
[A][B][A]
MANIFEST
- Unit square: 4in finished (4.5in cut w/ 1/4in seam allowance)
- Fabric: quilting cotton, 2 colorways
- Thread-to-unit ratio: standard piecing tension
FOUNDATION
- Cut 5x colorway A squares, 4x colorway B squares (4.5in each)
EXPANSION
- Row 1: sew A-B-A, press seams toward A
- Row 2: sew B-A-B, press seams toward B
- Row 3: sew A-B-A, press seams toward A
STABILIZATION
- Join Row1-Row2-Row3, nesting seams, maintain 1/4in allowance throughout
CONTRACTION
- Square block to 12.5in, trim excess, finish edges
EXCEPTION PROTOCOL
- If block measures off-square by >1/8in: re-press seams before trimming, do not trim to compensate.
Recommendation▾
Include a brief note on how to handle ambiguous or low-quality source photos, since 'reverse-engineering from a photo' is a stated use case but not addressed in pitfalls
Best Practices
- Kill adjectives. "Firm tension" → give the actual gauge number instead.
- Every row/step gets a number and a stitch count in parentheses — no ambiguity about where you are.
- Keep each node short enough to read on a phone screen without scrolling.
- Encode exceptions as conditionals (
if X deviates by Y, do Z), not as general advice. - When packaging for sale, strip all remaining narrative from the final payload — buyers get instructions, not backstory.
Common Pitfalls
- Don't blend phases — Expansion math and Stabilization math must never appear in the same block.
- Don't describe tension/gauge qualitatively ("keep it snug") — always give a measurable ratio or count.
- Don't skip the Prerequisite Manifest — without base counts declared, downstream rows can't be validated as dimensionally stable.
- Don't bury exception handling inline; keep it as a separate protocol block so the primary pipeline stays linear and clean.