add-puzzle-type

Solid

Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.

AI & Automation 26 stars 4 forks Updated today MIT

Install

View on GitHub

Quality Score: 81/100

Stars 20%
48
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Add Puzzle Type Scaffold a new puzzle type across all pipeline integration points in jigsawR. ## When to Use - Adding a completely new puzzle type to the package - Following the established integration checklist (CLAUDE.md 10-point pipeline) - Ensuring nothing is missed when wiring a new type end-to-end ## Inputs - **Required**: New type name (lowercase, e.g. `"triangular"`) - **Required**: Geometry description (how pieces are shaped/arranged) - **Required**: Whether the type needs external packages (add to Suggests) - **Optional**: Parameter list beyond the standard (grid, size, seed, tabsize, offset) - **Optional**: Reference implementation or algorithm source ## Procedure ### Step 1: Create Core Puzzle Module Create `R/<type>_puzzle.R` with the internal generation function: ```r #' Generate <type> puzzle pieces (internal) #' @noRd generate_<type>_pieces_internal <- function(params, seed) { # 1. Initialize RNG state # 2. Generate piece geometries # 3. Build edge paths (SVG path data) # 4. Compute adjacency # 5. Return list: pieces, edges, adjacency, metadata } ``` Follow the pattern in `R/voronoi_puzzle.R` or `R/snic_puzzle.R` for structure. **Got:** Function returns a list with `$pieces`, `$edges`, `$adjacency`, `$metadata`. **If fail:** Compare the return structure against `generate_voronoi_pieces_internal()` to identify missing list elements or incorrect types. ### Step 2: Wire into jigsawR_clean.R Edit `R/jigsawR_clean.R`: 1. Add `"<type>"` to...

Details

Author
pjt222
Repository
pjt222/agent-almanac
Created
1 years ago
Last Updated
today
Language
R
License
MIT

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

add-platform

Add support for a new AI coding tool, IDE, PR-reviewer, or context-packer to VibeTags — wire a new generated output file through ServiceRegistry, Platform, the renderer registry, and (if granular) GranularRulesWriter. Use when the user says "add platform support", "support <tool>", "generate a new output file for X", "new AI platform", or names an AI coding assistant/IDE/PR-reviewer/context-packer VibeTags doesn't yet generate a file for.

4 Updated 4 days ago
PIsberg
AI & Automation Featured

toolify

When you want to integrate an external tool, API, MCP server, or service into a project — the wizard walks you through auth, config, env vars, client wrapper code, example usage, and (optionally) a smoke-test. Scoped to Next.js and Rails projects (the two primary stacks). Interactive Q&A pattern — starts with the tool name, asks structured questions until the integration is fully specified, then scaffolds files. Examples of tools to toolify — Stripe, Kit, Sanity, Notion, Neon, Supabase, Fathom, Rewardful, SavvyCal, Riverside, ScrapeCreators, Anthropic, OpenAI, Gemini, Twilio, Resend, Postmark, Vercel Blob, custom internal APIs. For MCP servers specifically, also handles the .mcp.json wiring. Triggers on "/toolify," "integrate X," "add X to this project," "wire up X," "set up the X integration," "hook up X," "connect X," "add MCP for X." Part of the -ify trifecta (skillify / toolify / loopify) for extending Claude Code. NOT for adding new SKILL.md files — that's skillify. NOT for cron/agent loops — that's loop

229 Updated 2 days ago
coreyhaines31
AI & Automation Featured

add-source

Wire a new agent-CLI Source adapter into pixtuoid (a new coding CLI whose sessions become office sprites). Use when the user says 'add support for <CLI>', 'add a source for <tool>', or 'integrate <agent CLI>'. Orchestrates the cross-crate checklist whose steps have TEST TEETH — the ones a diff-scoped edit silently misses (site manifest bridge, per-source badge hue, home-dir fn, plus the two `pixtuoid/tests/*` integration goldens that `-p <crate> --lib` never builds).

425 Updated today
IvanWng97