Content site in production Architecture diagram showing reader requests moving through Cloudflare to an Astro origin, MDX bundle, and content CMS. CONTENT HTTPS SSR READ MDX QUERY EXT Reader Browser EDGE 01 Cloudflare Pages · cache ORIG 02 Astro Origin SSR + MDX BUN MDX Bundle src/content/*.mdx CMS Content CMS headless LEGEND Input External Focal Service Data store Primary flow HTTP / API Architecture Components, connections, trust boundaries
Should you write this as a skill? Flowchart showing when a new workflow should stay manual, become a project note, or be written as a reusable skill. NO YES NO YES New workflow Do it manually once Will you repeat it >3 times? One-off keep manual Reusable across projects? Project note project-scoped Write a skill reusable + assets LEGEND Start / end Step Decision Happy path Flowchart Decision logic and branching flows
Bearer call with token refresh Sequence diagram showing an API call that refreshes an expired access token before retrying. ALT [token valid] [expired] GET /ORDERS VERIFY JWT 200 ORDERS 401 EXPIRED REFRESH TOKEN NEW TOKEN AUDIT EVENT UI Client app SPA API API Gateway /v1 IDP Auth server OAuth 2.1 LEGEND Call Return Async Headline Sequence Messages between actors over time
Product launch · fourteen months Timeline showing product milestones from the first post in February 2025 through three design versions and the schematic skill in April 2026. 2025 2026 Q2 '25 Q3 '25 Q4 '25 Q1 '26 FEB 2025 First post APR 2025 Design v1 SEP 2025 Design v2 typography pass JAN 2026 Design v3 complexity budget APR 2026 · NOW Schematic skill eight diagram types LEGEND Event Major milestone Spacing is proportional to real elapsed time. Timeline Events on an honest time axis
Content ideas · Impact × Effort Impact-effort matrix showing eight content projects across do first, major projects, quick wins, and avoid quadrants. EFFORT IMPACT DO FIRST MAJOR PROJECTS QUICK WINS AVOID Schematic skill v4 Update changelog Design v4 refresh New publication Fix footer link Update OG tags Rewrite build pipeline Port to Nuxt LEGEND Do first Candidate Position is the signal. Colour is reserved for the single action item. Quadrant Two-axis positioning, 2×2
Order lifecycle State machine showing an order moving from placed through payment, packing and shipping to delivered, with a payment retry and separate cancel and failure outcomes. WAIT / RECOVERY TERMINAL PAY [OK] PAY [DECLINED] RETRY OK PICK DISPATCH SCAN CANCEL 3RD DECLINE Placed Paid Packed Shipped Delivered Payment retry ≤ 3 attempts Cancelled Failed * → Cancelled on customer request before dispatch LEGEND State Wait / recovery Start Happy path Recovery path State machine States, transitions, lifecycles
Refund request handoffs Swimlane showing how a refund request moves between the customer, support, finance and the payment provider. CUSTOMER SUPPORT FINANCE PAYMENT PROVIDER YES API 3–5 DAYS Request refund Triage ticket SLA 4h Eligible? Approve refund Issue refund API Money back LEGEND Start / end Step Decision Key handoff HTTP / API Async / return Swimlane Cross-functional handoffs
Payments platform · block decomposition Block decomposition of the payments platform into checkout, ledger and payouts, each with addressable sub-blocks. PAY-000 Payments platform PAY-001 Checkout PAY-002 Ledger PAY-003 Payouts PAY-001-01 Cart PAY-001-02 Card auth PAY-002-01 Journal PAY-002-02 Reconciliation LEGEND Block (ID badge) Focal Tree Hierarchy and block decomposition
Where controls are enforced Layer stack showing security controls grouped by the surface where they are enforced, from authoring down to runtime. L1 Authoring developer laptop pre-commit · secrets scan L2 Workspace GitHub org branch protection L3 Merge / CI pipeline SAST · 2 reviewers L4 Deploy Argo CD signed images L5 Runtime Kubernetes WAF · audit log LEGEND Request flows down Focal layer Layer stack Abstraction levels and controls
Orders data model Data model showing customers placing orders that contain line items referring to products. 1 0..* 1 1..* N 1 PLACES CONTAINS REFERS ENTITY Customer # id uuid email text name text ENTITY Order # id uuid → customer_id uuid status enum placed_at timestamptz ENTITY LineItem → order_id uuid → product_id uuid qty int ENTITY Product # id uuid sku text price numeric LEGEND Entity Relation · 1 / N cardinality Core relation ER / data model Entities, fields, cardinality