Python design patterns for CLI scripts and utilities — type-first development, deep modules, complexity management, and red flags. Use when reading, writing, reviewing, or refactoring Python files, especially in .trellis/scripts/ or any CLI/scripting context. Also activate when planning module structure, deciding where to put new code, or doing code review.
Guide for contributing to Trellis documentation and marketplace. Covers adding spec templates, marketplace skills, documentation pages, and submitting PRs across both the Trellis main repo and docs repo. Use when someone wants to add a new spec template, add a new skill to the marketplace, add or update documentation pages, or submit a PR to this project.
Discovers and injects project-specific coding guidelines from .trellis/spec/ before implementation begins. Reads spec indexes, pre-development checklists, and shared thinking guides for the target package. Use when starting a new coding task, before writing any code, switching to a different package, or needing to refresh project conventions and standards.
Adapts an external skill into project-specific development guidelines in .trellis/spec/. Creates guideline sections, code example templates with .template suffix, and updates spec indexes. Use when integrating an external skill, adding a new skill's patterns to project conventions, or incorporating third-party skill best practices into .trellis/spec/ documentation.
Real-time web search using Playwright-controlled browser. Use this skill when you need current information, latest documentation, recent news, or any data beyond your knowledge cutoff (January 2025).
Create a concise plan. Use when a user explicitly asks for a plan related to a coding task.
Analyze existing source code to identify key patterns and generate comprehensive educational skill documentation with proper YAML frontmatter, architectural analysis, code templates, and usage examples.
Generate properly-formatted SKILL.md files from extracted architectural patterns. Turns raw pattern descriptions into reusable skills that OpenSpace can discover, select, and evolve.
Unified document generation with tool failure detection, domain knowledge fallback, progressive conversion, and Unicode safety
Systematic workflow to resolve FileNotFoundError by locating and verifying file paths
Systematic debugging workflow for pandoc PDF conversion errors
Iterative workflow to verify PDF page counts and adjust layout parameters until requirements are met
Handle tool failures when researching regulatory/government content by using fallback methods and domain knowledge
Handle web research failures by pivoting to internal knowledge for content generation
Heuristic for detecting search tool failures and pivoting to domain knowledge for document generation
Safely update Excel workbooks by first locating candidate files, verifying workbook structure before editing, and running post-write validation against required sheets, populated columns, and sample counts.
Systematic workflow for troubleshooting SSL/proxy connectivity issues with government websites
Search for reusable skills across OpenSpace's local registry and cloud community. Reusing proven skills saves tokens, improves reliability, and extends your capabilities beyond built-in tools.
Systematic workflow for auditing TypeScript codebases for import hygiene issues (value vs. type imports, duplicates), missing base class extensions, and incomplete barrel file re-exports, with actionable fix patterns.
Diagnose and resolve file access issues by first verifying the directory structure.
Generate structured medical SOAP notes with all required sections in a single comprehensive file write.
Create structured medical SOAP notes by writing comprehensive content to a file in one iteration
Generate professional documents using write_file when primary data sources fail, leveraging embedded domain knowledge instead of external retrieval
IMMEDIATELY USE THIS SKILL when creating or develop anything and before writing code or implementation plans - refines rough ideas into fully-formed designs through structured Socratic questioning, alternative exploration, and incremental validation
