cookmode-v2-source-of-truth
Documents and explains the CookMode V2 codebase as it exists. Use this when the user needs factual information about the current implementation, architecture, file locations, or how components work. DOES NOT suggest improvements unless explicitly asked.
Best use case
cookmode-v2-source-of-truth is best used when you need a repeatable AI agent workflow instead of a one-off prompt. It is especially useful for teams working in multi. Documents and explains the CookMode V2 codebase as it exists. Use this when the user needs factual information about the current implementation, architecture, file locations, or how components work. DOES NOT suggest improvements unless explicitly asked.
Documents and explains the CookMode V2 codebase as it exists. Use this when the user needs factual information about the current implementation, architecture, file locations, or how components work. DOES NOT suggest improvements unless explicitly asked.
Users should expect a more consistent workflow output, faster repeated execution, and less time spent rewriting prompts from scratch.
Practical example
Example input
Use the "cookmode-v2-source-of-truth" skill to help with this workflow task. Context: Documents and explains the CookMode V2 codebase as it exists. Use this when the user needs factual information about the current implementation, architecture, file locations, or how components work. DOES NOT suggest improvements unless explicitly asked.
Example output
A structured workflow result with clearer steps, more consistent formatting, and an output that is easier to reuse in the next run.
When to use this skill
- Use this skill when you want a reusable workflow rather than writing the same prompt again and again.
When not to use this skill
- Do not use this when you only need a one-off answer and do not need a reusable workflow.
- Do not use it if you cannot install or maintain the related files, repository context, or supporting tools.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cookmode-v2-source-of-truth/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cookmode-v2-source-of-truth Compares
| Feature / Agent | cookmode-v2-source-of-truth | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Documents and explains the CookMode V2 codebase as it exists. Use this when the user needs factual information about the current implementation, architecture, file locations, or how components work. DOES NOT suggest improvements unless explicitly asked.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# CookMode V2 Source of Truth Agent ## Your Role You are a **documentation-only agent**. Your sole purpose is to create accurate technical maps of the existing CookMode V2 system. ## CRITICAL CONSTRAINTS **DO NOT:** - Suggest improvements or changes unless the user explicitly asks - Perform root cause analysis unless the user explicitly asks - Propose future enhancements unless the user explicitly asks - Critique the implementation or identify problems - Recommend refactoring, optimization, or architectural changes **ONLY:** - Describe what exists - Explain where it exists - Document how it works - Map how components interact - Provide factual technical information ## When to Use This Skill Invoke this skill when the user needs: - "What does this component do?" - "How does feature X work?" - "Where is Y implemented?" - "What files are involved in Z?" - "Document the current state of..." - "Explain how the recipe data flows through the system" ## Project Structure Reference ### Core Architecture - **Frontend**: Vanilla React (React.createElement, no JSX) - **CSS Framework**: Pico CSS v2 (~10kb, classless, semantic HTML) - **Styling Philosophy**: ZERO custom CSS goal - use semantic HTML + Pico variables only - **Database**: Supabase (PostgreSQL with real-time subscriptions) - **State Management**: React hooks (useState, useEffect, custom hooks) ### Key Directories ``` cookmodeV2/ ├── index.html # Main entry point ├── recipes.js # Recipe data definitions ├── js/ │ ├── components/ # React components (RecipeGrid, RecipeModal, etc.) │ ├── hooks/ # Custom React hooks (useRecipeData, useRealtime, useSupabase) │ ├── utils/ # Utility functions (scaling, formatting) │ └── constants/ # Status constants and styling configs ├── styles/ │ └── main.css # Custom Pico CSS overrides (~330 lines) └── supabase-schema.sql # Database schema ``` ### Component Flow 1. **App.js** → Root component 2. **RecipeGrid.js** → Displays recipe cards with filters 3. **RecipeModal.js** → Shows recipe details when card is clicked 4. **Lightbox.js** → Image viewer for recipe photos ### Data Flow 1. `useSupabase()` → Initializes Supabase client 2. `useRecipeData()` → Manages recipe state (ingredients, steps, status) 3. `useRealtime()` → Syncs changes across clients via Supabase subscriptions 4. Local state updates → Optimistic UI → Supabase persistence ## How to Document When documenting, provide: 1. **What**: Clear description of the component/feature 2. **Where**: File paths and line numbers 3. **How**: Implementation details and patterns 4. **Interactions**: Dependencies and data flow ### Example Output Format ```markdown ## Feature: Recipe Scaling **What**: Allows users to scale ingredient quantities based on order count (1-50x) **Where**: - `/js/components/RecipeModal.js:119-131` - Slider UI and handler - `/js/utils/scaling.js:3-20` - scaleAmount() function - `/js/hooks/useRecipeData.js` - orderCounts state management **How**: - User adjusts slider (1-50 range) - handleOrderChange() validates and updates orderCounts state - scaleAmount() multiplies ingredient quantities by orderCount - Ingredients re-render with scaled amounts **Interactions**: - Updates Supabase `recipe_order_counts` table - Real-time sync via useRealtime() hook ``` ## Recent Project Changes (Context) ### Styling Philosophy (Current) - **Goal**: ZERO custom CSS - rely entirely on Pico CSS - **Principle**: If you need custom CSS, you're using the wrong HTML element - **Current State**: ~330 lines in main.css (target: minimal or zero) - **Approach**: Semantic HTML first, Pico variables second, custom CSS last resort **Decision Tree for Styling**: 1. Try semantic HTML element (dialog, mark, article, etc.) 2. Use Pico CSS variable (--pico-primary, --pico-spacing, etc.) 3. Inline style for positioning/sizing only 4. Custom CSS only if absolutely necessary (document why) ### CSS Simplification (Recent) - Migrated from Tailwind utilities to Pico CSS - Reduced custom CSS from 1030 lines → 330 lines - Used semantic HTML5 elements (dialog, article, section, fieldset) - Target: Further reduce to near-zero custom CSS ### Removed Features - Ingredient/step metadata tracking (checked_by, checked_at) - Shopping list feature - Complex inline styles - Tailwind utility classes ### Database Tables - `ingredient_checks` - Tracks checked ingredients - `step_checks` - Tracks checked steps - `recipe_status` - Recipe workflow status (gathered, complete, plated, packed) - `recipe_order_counts` - Order quantities - `recipe_chef_names` - Chef assignments with color badges ## Output Guidelines - Use markdown formatting - Include file paths with line numbers - Show code snippets only when necessary - Use bullet points for clarity - Link related components - Stay factual and objective Remember: You are a technical cartographer, not an architect. Map what exists, don't redesign it.
Related Skills
opensource-guide-coach
Use when a user wants guidance on starting, contributing to, growing, governing, funding, securing, or sustaining an open source project, or asks about contributor onboarding, community health, maintainer burnout, code of conduct, metrics, legal basics, or open source project adoption.
azure-resource-manager-sql-dotnet
Azure Resource Manager SDK for Azure SQL in .NET. Use for MANAGEMENT PLANE operations: creating/managing SQL servers, databases, elastic pools, firewall rules, and failover groups via Azure Resource Manager. NOT for data plane operations (executing queries) - use Microsoft.Data.SqlClient for that. Triggers: "SQL server", "create SQL database", "manage SQL resources", "ARM SQL", "SqlServerResource", "provision Azure SQL", "elastic pool", "firewall rule".
azure-resource-manager-redis-dotnet
Azure Resource Manager SDK for Redis in .NET. Use for MANAGEMENT PLANE operations: creating/managing Azure Cache for Redis instances, firewall rules, access keys, patch schedules, linked servers (geo-replication), and private endpoints via Azure Resource Manager. NOT for data plane operations (get/set keys, pub/sub) - use StackExchange.Redis for that. Triggers: "Redis cache", "create Redis", "manage Redis", "ARM Redis", "RedisResource", "provision Redis", "Azure Cache for Redis".
azure-resource-manager-postgresql-dotnet
Azure PostgreSQL Flexible Server SDK for .NET. Database management for PostgreSQL Flexible Server deployments. Use for creating servers, databases, firewall rules, configurations, backups, and high availability. Triggers: "PostgreSQL", "PostgreSqlFlexibleServer", "PostgreSQL Flexible Server", "Azure Database for PostgreSQL", "PostgreSQL database management", "PostgreSQL firewall", "PostgreSQL backup", "Postgres".
azure-resource-manager-playwright-dotnet
Azure Resource Manager SDK for Microsoft Playwright Testing in .NET. Use for MANAGEMENT PLANE operations: creating/managing Playwright Testing workspaces, checking name availability, and managing workspace quotas via Azure Resource Manager. NOT for running Playwright tests - use Azure.Developer.MicrosoftPlaywrightTesting.NUnit for that. Triggers: "Playwright workspace", "create Playwright Testing workspace", "manage Playwright resources", "ARM Playwright", "PlaywrightWorkspaceResource", "provision Playwright Testing".
azure-resource-manager-cosmosdb-dotnet
Azure Resource Manager SDK for Cosmos DB in .NET. Use for MANAGEMENT PLANE operations: creating/managing Cosmos DB accounts, databases, containers, throughput settings, and RBAC via Azure Resource Manager. NOT for data plane operations (CRUD on documents) - use Microsoft.Azure.Cosmos for that. Triggers: "Cosmos DB account", "create Cosmos account", "manage Cosmos resources", "ARM Cosmos", "CosmosDBAccountResource", "provision Cosmos DB".
azure-resource-visualizer
Analyze Azure resource groups and generate detailed Mermaid architecture diagrams showing the relationships between individual resources. USE FOR: create architecture diagram, visualize Azure resources, show resource relationships, generate Mermaid diagram, analyze resource group, diagram my resources, architecture visualization, resource topology, map Azure infrastructure DO NOT USE FOR: creating/modifying resources (use azure-deploy), security scanning (use azure-security), performance troubleshooting (use azure-diagnostics), code generation (use relevant service skill)
azure-resource-lookup
List, find, and show Azure resources. Answers "list my VMs", "show my storage accounts", "list websites", "find container apps", "what resources do I have", and similar queries for any Azure resource type. USE FOR: list resources, list virtual machines, list VMs, list storage accounts, list websites, list web apps, list container apps, show resources, find resources, what resources do I have, list resources in resource group, list resources in subscription, find resources by tag, find orphaned resources, resource inventory, count resources by type, cross-subscription resource query, Azure Resource Graph, resource discovery, list container registries, list SQL servers, list Key Vaults, show resource groups, list app services, find resources across subscriptions, find unattached disks, tag analysis. DO NOT USE FOR: deploying resources (use azure-deploy), creating or modifying resources, cost optimization (use azure-cost-optimization), writing application code, non-Azure clouds.
mcp-resources-guide
Implement MCP resources that provide data and files to AI assistants - URIs, caching, and streaming
get-available-resources
This skill should be used at the start of any computationally intensive scientific task to detect and report available system resources (CPU cores, GPUs, memory, disk space). It creates a JSON file with resource information and strategic recommendations that inform computational approach decisions such as whether to use parallel processing (joblib, multiprocessing), out-of-core computing (Dask, Zarr), GPU acceleration (PyTorch, JAX), or memory-efficient strategies. Use this skill before running analyses, training models, processing large datasets, or any task where resource constraints matter.
resource-monitor
Monitor system resources (CPU, memory, disk, network) during development and production.
docs-sources
Knowledge of documentation platforms and fetching strategies. Use when adding new documentation sources, determining fetch strategy for a docs site, detecting doc frameworks, or configuring the docs registry.