CookMode V2 Source of Truth
Map the Current CookMode V2 Codebase
Understanding an unfamiliar codebase is slow when architecture and file ownership are unclear. This skill produces factual maps of CookMode V2 components, data flow, and implementation locations.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "CookMode V2 Source of Truth" from https://skillstore.io/skills/adamfehse-cookmode-v2-source-of-truth.md and its manifest at https://skillstore.io/api/skills/adamfehse-cookmode-v2-source-of-truth/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "CookMode V2 Source of Truth". Where is recipe scaling implemented?
Expected outcome:
- Recipe scaling is documented in RecipeModal, the scaling utility, and the recipe-data hook.
- The flow updates order counts, recalculates ingredient quantities, and persists the order count through Supabase.
Using "CookMode V2 Source of Truth". How does real-time synchronization work?
Expected outcome:
- The documented flow initializes Supabase, manages recipe state through a custom hook, and uses a real-time hook for client synchronization.
- Local changes update the interface before persistence and subscription updates.
Security Audit
SafeAll 15 static external-command detections are false positives caused by Markdown fences and inline code formatting in SKILL.md. The skill contains documentation guidance only; no executable shell or Ruby command is present. No prompt-injection, credential-exfiltration, or destructive intent was found.
Risk Factors
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/adamfehse-cookmode-v2-source-of-truth/audits/11?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/adamfehse-cookmode-v2-source-of-truth?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/adamfehse-cookmode-v2-source-of-truth?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/adamfehse-cookmode-v2-source-of-truth/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/adamfehse-cookmode-v2-source-of-truth.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
AdamFehse. (2026). CookMode V2 Source of Truth security audit report (audit version 11) [Author version unspecified]. Skillstore. https://skillstore.io/skills/adamfehse-cookmode-v2-source-of-truth/audits/11BibTeX citation
@techreport{adamfehse-adamfehse-cookmode-v2-source-of-truth-2026,
author = {AdamFehse},
title = {CookMode V2 Source of Truth security audit report (audit version 11)},
institution = {Skillstore},
year = {2026},
number = {11},
url = {https://skillstore.io/skills/adamfehse-cookmode-v2-source-of-truth/audits/11},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "CookMode V2 Source of Truth security audit report (audit version 11)"
version: "unspecified"
type: report
authors:
- name: "AdamFehse"
date-released: "2026-07-18"
url: "https://skillstore.io/skills/adamfehse-cookmode-v2-source-of-truth/audits/11"
identifiers:
- type: other
value: "skillstore:adamfehse-cookmode-v2-source-of-truth:audit:11"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Onboard to the recipe application
Request a map of the main components and data flow before making your first change.
Locate a feature implementation
Find the documented files and interactions behind recipe scaling or real-time updates.
Prepare technical handoff notes
Create a factual overview of the current architecture for teammates or stakeholders.
Try These Prompts
Explain what RecipeModal does in CookMode V2. Include where it fits in the component flow.
Describe how recipe data moves from local state to Supabase and back to connected clients.
Document the current recipe-scaling feature. Include the relevant files, documented line ranges, data changes, and interactions.
Create a factual Markdown architecture map for CookMode V2. Cover frontend structure, hooks, Supabase integration, styling, and database tables. Do not suggest changes.
Best Practices
- Ask for a specific feature, component, or data path when possible.
- Request file paths and interactions when preparing implementation work.
- Ask explicitly for analysis or recommendations if you need more than factual documentation.
Avoid
- Do not treat the documentation as proof that the current repository has not changed.
- Do not expect unsolicited refactoring or performance recommendations.
- Do not use this skill as a substitute for testing runtime behavior.