Query float.db for full context on a file or folder. Use when user mentions a path, asks about folder context, says "what do we know about X?", or BEFORE modifying any unfamiliar code. Proactive use prevents mistakes.
Guide OAK engineering constitution creation with decision-driven requirements, requirement language patterns, and reality-grounded standards.
Generate targeted clarifying questions (2-3 max) that challenge vague requirements and extract missing context. Use after request-analyzer identifies clarification needs, before routing to specialist agents. Helps cto-orchestrator avoid delegating unclear requirements.
This skill should be used when the user asks about Railway features, how Railway works, or shares a docs.railway.com URL. Fetches up-to-date Railway docs to answer accurately.
Proactively update SKILL.md files when they become outdated, incorrect, or need improvements. Use when you notice a skill doesn't match current workflow, when user corrects your skill usage, or when discovering better practices that should be documented.
Displays the roster of architecture team members with their specialties and expertise areas. Use when the user asks "Who's on the architecture team?", "List architecture members", "Show me the architects", "What specialists are available?", "Who can I ask for reviews?", or wants to discover available experts. Do NOT use for requesting reviews (use specialist-review or architecture-review) or checking documentation status (use architecture-status).
Reports on the health and state of architecture documentation (counts of ADRs, reviews, activity levels, documentation gaps). Use when the user asks "What's our architecture status?", "Show architecture documentation", "How many ADRs do we have?", "What decisions are documented?", "Architecture health check", or wants an overview/summary of documentation state. Do NOT use for listing team members (use list-members), creating new documents (use create-adr), or conducting reviews (use architecture-review or specialist-review).
Skill for enforcing and documenting the application's brand colors and fonts. Use this skill to ensure all UI components and pages reflect the official brand identity.
This skill should be used when the user asks to "create problem", "problem record", "root cause analysis", "RCA", "known error", "KEDB", "problem investigation", or any ServiceNow Problem Management development.
Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.
Create comprehensive technical roadmaps aligned with business goals. Plan technology investments, architecture evolution, and infrastructure improvements over quarters and years.
Organize and structure information for clarity and discoverability. Design navigation systems, hierarchies, and mental models that match user needs.
Transform brain dumps into polished blog posts in Nick Nisi's voice. Use when the user wants to write a blog post with scattered ideas, talking points, and conclusions that need organization into a cohesive narrative with Nick's conversational, authentic, and thoughtful tone.
Brief description of what this Skill does and when to use it. Include specific trigger phrases. Use when user asks "trigger phrase 1", "trigger phrase 2", or wants to [outcome]. Max 1024 characters.
Mine Codex sessions to synthesize your top software design heuristics (no quotes, no evidence).
Analyze recent conversation to identify improvements for CLAUDE.md memory files. Trigger when user says "reflect on this session", "reflect on this conversation", "reflect on this code", or "improve CLAUDE.md by reflecting on this session". The verb "reflect" combined with a session/conversation/code subject is the key trigger.
