openscad-workshop-tools
Create parametric OpenSCAD 3D models of workshop tools (drill presses, vacuums, saws, etc.) for workshop layout planning. Use when asked to "model a tool", "create OpenSCAD for [tool]", "add [tool] to workshop", or when planning workshop layouts that need tool representations. Supports brand-accurate colors (Bosch, Festool, Makita, DeWalt, Milwaukee) and standardized code structure with customizer parameters.
What this skill does
# OpenSCAD Workshop Tool Modeling
Create parametric 3D models of workshop tools for layout planning and visualization.
## Workflow
### 1. Gather Specifications
Collect from user, manuals, or product pages:
- **Dimensions**: Overall W x D x H, base plate size
- **Weight**: Helps verify scale is reasonable
- **Key features**: Chuck size, motor power, speeds (for header comment)
- **Reference image**: Essential for component identification
### 2. Identify Components
Decompose tool into logical modules. See [references/code-structure.md](references/code-structure.md) for decomposition patterns by tool type.
Typical components:
- Base/frame (static foundation)
- Main body/motor housing
- Moving parts (quill, blade guard, plunge mechanism)
- Controls (buttons, dials, levers)
- Accessories (vise, fence, dust port)
### 3. Write OpenSCAD File
Follow the standardized structure in [references/code-structure.md](references/code-structure.md):
```openscad
/* [Section] */ // Customizer sections
// Comment // Parameter description
param = value; // Actual parameter
module component() { ... } // One module per component
module tool_name() { ... } // Assembly module
tool_name(); // Render call
echo("=== ... ==="); // Debug output
```
**Key patterns:**
- Use `$fn = $preview ? 32 : 64` for quality switching
- Apply brand colors from reference table
- Include `show_*` toggles for optional components
- Use `hull()` for rounded shapes
- Add floor reference plane for context
### 4. Render Preview
```bash
openscad -o images/tool-name.png \
--autocenter --viewall \
--imgsize=800,1000 \
/path/to/tool.scad
```
### 5. Iterate
Adjust proportions based on visual comparison to reference image.
## File Location
Save to: `workshop/tools/<brand>-<model>.scad`
Examples:
- `workshop/tools/bosch-pbd40.scad`
- `workshop/tools/festool-ctl-midi.scad`
- `workshop/tools/festool-ts55.scad`
## Quick Reference
| Tool Type | Key Dimensions | Critical Components |
|-----------|---------------|---------------------|
| Drill press | Base, column height, head depth | Column, quill, chuck, handwheel |
| Track saw | Body L x W x H, blade dia | Base plate, blade guard, handle |
| Vacuum | L x W x H, wheel dia | Body, wheels, handle, hose port |
| Bandsaw | Table size, throat depth | Frame, table, blade guides |
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".