hoangsonww

MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supported language. Use…

MANDATORY for every coding agent and contributor touching localized content — keep all five localization surfaces (dashboard UI keys, wiki page, mirrored READMEs, locale-aware formatting, language switchers) in parity across every supported language. Use…

MANDATORY for every coding agent (Claude Code, Codex, or any other) — keep this repository's documentation in sync after any change to behavior, configuration, interfaces, events, schema, or features. Use automatically (without being asked) at the end of ANY…

Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.

MANDATORY for every coding agent (Claude Code, Codex, or any other) on every change-set — every applicable source file the agent creates or updates MUST start with the project's copyright/authorship header (file overview + exact author line). Use…

Choose and apply the correct semantic version bump for this repository. Use for every user-visible release, before merge when a change set should ship as patch, minor, or major, and whenever package/plugin/desktop version metadata must stay synchronized.

Push the current working tree directly to a GitHub PR whose head lives on a **fork**, without creating a new branch and without pushing to `origin` (which is usually the upstream). Invoke when the user says things like "push straight to PR

Push the current working tree directly to a GitHub PR whose head lives on a **fork**, without creating a new branch and without pushing to `origin` (which is usually the upstream). Invoke when the user says things like "push straight to PR

Deep review — random exploration + cross-agent review, alternating. Finds integration bugs that self-review misses. Run every 30–60 min during active implementation.

Overview of Forge's Agentic Coding Flywheel methodology. Use to route between plan, bead, and code space. See FLYWHEEL.md at the repo root.

End-of-session ritual. Close finished beads, file new ones for remaining work, run verify, commit in logical groupings, push. Work is not complete until git push succeeds.

Start a new Flywheel planning round. Produce initial markdown plan, route to competing frontier models, synthesize hybrid, refine 4–5×. Use before any coding begins on a new feature.

Translate a polished markdown plan into self-contained beads in .beads/beads.jsonl. Every bead must be executable without reopening the plan. Use after the plan has converged.

Polishing pass over all open beads. Run 4–6 times. "Check your beads N times, implement once." Use after plan-to-beads and between refinement rounds.

Break the spell of local productivity. Ask whether completing all open beads actually closes the gap to the project goal. Use at milestones or when busy agents feel directionally off.

Remove telltale AI-writing patterns from README, docs, and user-facing text. Must be done line-by-line, manually. No regex. Use after agents write any user-visible prose.

Conducts deep competitive intelligence on a target product or company, mapping out rivals, feature gaps, and market sentiment.

Provides fundamental analysis of crypto projects by analyzing tokenomics, whitepapers, and community sentiment.

Synthesizes a comprehensive financial briefing on a public company using recent earnings calls, SEC filings, and financial news.

Researches any topic across Reddit, X, YouTube, HN, Polymarket, and the web from the last 30 days, synthesizing a grounded summary based on human engagement.

Finds the latest research papers on a specific topic, summarizes their core contributions, and explains complex methodology in plain English.

Extracts transcripts from podcasts or videos and synthesizes actionable takeaways.

Analyzes a GitHub repository for health, security, and maintenance metrics.

Identifies emerging early-stage startups in a specific sector using funding data and launch platforms.

PetSwipe workflow for checking whether deployment, production-readiness, or enterprise-grade claims are actually supported by repo evidence. Use when editing deployment docs, infra summaries, or any task that makes strong statements about readiness.

PetSwipe map and geocoding workflow for diagnosing map page issues, geocode request volume, cache behavior, API proxy behavior, CORS issues, and location-related UI regressions. Use when the task mentions the map page, geocoding, location results, or geocode…

PetSwipe navigation workflow for navbar changes, icon-only links, mobile menu behavior, route placement, and page discoverability. Use when work changes the navbar, mobile navigation, page ordering, or the relationship between key user-facing pages.

PetSwipe workflow for adoption-planner and insights page work, including comparison cards, gauges, charts, metrics, and recommendation panels. Use when changes focus on adoption-planner.tsx, insights.tsx, or the relationship between liked pets, readiness, and…

PetSwipe validation workflow for choosing the smallest reliable checks for frontend, backend, infra, docs, and mixed changes. Use when a task needs a concrete validation plan or when the repo's pre-existing lint or type issues make broad validation noisy.

Backend-local workflow for health endpoints, readiness behavior, Swagger/OpenAPI exposure, and runtime contract changes in PetSwipe. Use when backend work touches backend/src/app.ts, startup behavior, docs endpoints, or deployment-sensitive runtime behavior.

Docs-local workflow for keeping PetSwipe product pages, deployment docs, architecture docs, and operational claims aligned with the current repository. Use when working inside docs or when multiple docs need to be updated together.

Frontend-local workflow for PetSwipe chart overflow, tooltip, dark mode text, clipping, and responsive layout issues inside frontend pages and shared chart components. Use when working in frontend and the issue is specifically about charts or mobile layout…

Regenerate docs/screenshots from the live apps. Use when UI changed and README/docs images are stale, or the user asks for new screenshots.

Change Mac, iOS, iPad, or Watch UI that sits on DiffuseUI. Use when a screen, widget, complication, or menu-bar extra is involved.

Generate first-party Swift package coverage (llvm-cov HTML, lcov, text summary). Use when the user asks for coverage, after expanding Tests/, or before claiming test work is done.

Add something Diffuse can observe on a device (typed capability, collector, registry line, and tests). Use when the user wants a new collector, observable, or capability ID.

Change or debug the diffuse-dev CLI (capture, inspect, diff, validate, fixtures, privacy). Use when adding a command or the CLI disagrees with the apps.

Split and describe a git commit for Diffuse. Use when the user asks to commit, or when a change should be multiple commits.

Type-check shared packages against the iOS and watchOS SDKs. Use after editing core packages, before verify, or when CI crosscheck fails.

Diagnose a collector that hangs, throws, records a placeholder, or produces noisy diffs. Use when a section is failed, timed out, permission-required, or a live capture is unstable.

Use this skill when working anywhere in the SynthoraAI monorepo and you need the repository-specific operating model: which service owns what, which commands are canonical, which wrappers are stale, how to choose tests, and which paths are generated or risky…

Change or review the Python agentic_ai subsystem or Codex-facing MCP integration for this repository. Use when work touches agentic_ai/, the LangGraph pipeline, the mcp_server package, .mcp.json, or cloud adapters for the agentic pipeline.

Audit this repository for docs-to-code drift, broken paths, stale wrappers, inconsistent environment assumptions, or other mismatches between implementation and operational guidance. Use when Codex needs to verify whether repo docs, scripts, schedules,…

Use this skill when working on the Python agentic_ai subsystem or Claude Code MCP integration for this repository, including the LangGraph pipeline, local MCP server, cloud adapters, and the project .mcp.json configuration.

Use this skill when you want Claude Code to audit this repository for docs-to-code drift, broken paths, stale scripts, inconsistent environment assumptions, or mismatches between implementation and operational docs.

Change or review the backend API, auth, controllers, models, sitewide chat backend, Gemini integration, Pinecone integration, or backend maintenance scripts in this repository. Use when work touches backend/ routes, controllers, services, models, scheduled…

Change or review the Next.js frontend in this repository. Use when work touches frontend/pages, frontend/components, frontend/services, auth UX, article detail flows, sitewide chat UI, browser-only state, or Pages Router behavior.

Change or review infrastructure, deployment, or rollout logic in this repository. Use when work touches infrastructure/, Terraform, Kubernetes manifests, monitoring config, deployment wrappers, or environment-specific operational assumptions.

Work on EstateWise MCP, agentic-ai, web-grounding, token flows, and A2A integrations. Use when changing tool behavior, orchestration, runtime flags, MCP wrappers, HTTP/A2A endpoints, or AI integration paths.

Extend or audit Codex support in the EstateWise repository. Use when changing .codex config, .codex/rules, .agents/skills, AGENTS.md layering, multi-agent roles, project guidance discovery, or Codex-specific documentation and workflows.

Audit producer-consumer alignment in EstateWise when REST, tRPC, MCP, gRPC, A2A, or shared payloads may have changed. Use when one package's change could silently break another package, tool, or doc set.

Execute production-safe code changes in the EstateWise monorepo. Use when implementing or fixing behavior in backend, frontend, MCP, agentic-ai, gRPC, deployment-control, tests, or repo docs. Do not use for pure brainstorming, skill installation, or work…

Run or debug the EstateWise local environment. Use when setting up services, choosing the smallest service combination, checking local endpoints, or troubleshooting environment/config issues. Do not use for routine code implementation unless local…

Work on EstateWise deployment-control, Docker, Kubernetes, Helm, Terraform, Jenkins, and cloud deployment assets. Use for infrastructure and operational workflow changes, not ordinary application feature work.

Review EstateWise changes for correctness, regressions, security issues, contract mismatches, operational risk, and missing tests. Use for PR review, diff review, bug hunts, and branch-vs-main analysis. Do not use for implementation tasks unless the user asks…

Playbook for MCP, agentic-ai, web-grounding, token flows, and A2A in EstateWise. Use when changing tool calls, orchestration, runtime behavior, or AI integration paths.

MDX article conventions for DevVerse. Use when adding or editing files under content/, changing article metadata, updating author or date lines, or modifying code that parses article content for feeds, related posts, reading stats, or RAG ingestion.

Feed, sitemap, metadata, and publishing guidance for DevVerse. Use when modifying lib/rss.ts, lib/jsonfeed.ts, feed routes, next-sitemap.config.js, app/layout.tsx metadata, manifest or robots files, or SEO-related site metadata.

DevVerse chat, citation, and retrieval workflow. Use when modifying the chat page, the chat API route, citation parsing, local retrieval fallback, Pinecone or Gemini integration, or the article vectorization pipeline.

Refresh Pinecone article embeddings after MDX article changes or RAG chunking and metadata changes. Use when content updates should be reflected in chat retrieval or when the vectorization pipeline changes.

Supabase auth, favorites, and security boundaries for DevVerse. Use when changing files under supabase/, auth or favorites UI, or the verify-email and reset-password API routes.

Route and UI conventions for the DevVerse Next.js app. Use when modifying app routes, layout, navigation, page components, global styling, route-scoped CSS, article rendering, favorites UI, or chat UI.

Run repository-specific validation for DevVerse changes. Use when asked to test, validate, smoke check, or confirm modifications in this repository.

MDX article conventions for DevVerse. Use when adding or editing files under content/, changing article metadata, updating author or date lines, or modifying code that parses article content for feeds, related posts, reading stats, or RAG ingestion.

Coordinate gameplay, persistence, UX, or accessibility changes that must remain consistent across the web, iOS, and Android 2048 clients.

Implement or review the Jetpack Compose 2048 app, its ViewModel and storage, Material UI, Gradle build, or emulator tests.

Implement or review the native SwiftUI 2048 app, its ViewModel, persistence, accessibility, XCTest coverage, or simulator flows.

Implement or review the 2048 browser client, including its rules engine, responsive UI, accessibility, PWA metadata, screenshots, or SEO.

Perform final release-readiness validation for the 2048 repository, including tests, builds, screenshots, metadata, documentation, and a scoped findings report.

Implement or review the Compose 2048 client, ViewModel, persistence, Gradle build, or emulator flows.

Coordinate behavior and UX changes across the web, iOS, and Android 2048 clients.

Implement or review the SwiftUI 2048 client, ViewModel, persistence, accessibility, tests, or simulator flows.

Execute the Flywheel bead lifecycle — find, claim, implement, review, close

Manage the WealthWise Docker/Podman Compose development environment. Triggers when asked to "start Docker", "start Podman", "bring up the containers", "stop Docker", "show Docker logs", or "restart the dev environment". Does NOT trigger implicitly.

Check the health of the running WealthWise API, web app, and MongoDB services. Triggers when asked to "check if the app is running", "verify the API is up", "is the server healthy", or "show service status".

Scaffold a complete new API endpoint for the WealthWise Express API. Triggers when asked to "add an endpoint", "create a route", "build an API for <entity>", or scaffold any new REST resource end-to-end. Does not trigger for frontend-only tasks.

Seed the WealthWise MongoDB database with categories or demo data. Triggers when asked to "seed the database", "add demo data", "populate categories", or "set up test data". Does NOT trigger implicitly during general development tasks.

Scaffold a new Mongoose model and its CRUD service for the WealthWise API. Triggers when asked to "create a model", "add a Mongoose schema", or add the data layer for a new entity without a full endpoint. Does NOT scaffold routes, controllers, or frontend…

Scaffold a complete new Next.js dashboard page for the WealthWise web app. Triggers when asked to "add a page", "create a dashboard screen", "build a UI for <feature>", or scaffold any new frontend feature end-to-end. Does not trigger for API-only or backend…

Run the full WealthWise pre-PR checklist and report a pass/fail for each gate. Triggers when asked to "run pre-PR checks", "check if this is ready to merge", "validate before opening a PR", or "run the full check". Does NOT trigger implicitly.

Work on Lumina deployment and infrastructure assets. Use when editing terraform/, aws/, docker-compose.yml, DEPLOYMENT.md, ADVANCED_DEPLOYMENTS.md, agentic_ai/deployments/, or other files related to Docker, Terraform, AWS or Azure rollout behavior,…

Work on the Python multi-agent pipeline and MCP client in agentic_ai. Use when editing files under agentic_ai/, changing agent orchestration, configuration loading, MCP client connectivity, async execution flow, pipeline startup commands, or cloud deployment…

Develop and maintain the standalone Lumina MCP server. Use when editing files under mcp_server/, adding or modifying tools, resources, prompts, middleware, configuration, or transport behavior for the Model Context Protocol server.

Implement and debug the Express and TypeScript backend for Lumina. Use when editing files under server/src or server/package.json, changing authentication, conversations, guest flows, chat routes, models, middleware, API contracts, or Gemini and Pinecone…

Build, refine, and debug the React/Vite frontend for Lumina. Use when editing files under client/src or client/package.json, changing chat UX, landing page content, auth flows, routing, theme behavior, markdown rendering, animations, responsive layout, or…

Manage Lumina's retrieval-augmented generation and knowledge ingestion workflow. Use when editing server/src/services/knowledgeBase.ts, server/src/services/pineconeClient.ts, server/src/scripts/knowledgeCli.ts, server/src/models/KnowledgeSource.ts, files…

Guide for changing SymptomSync's Python symptom-analysis service under agentic_ai/. Use when tasks touch the FastAPI service, LangGraph flow, agents, chains, settings, tests, monitoring, or deployment configuration for the agentic_ai workspace.

Guide for changing SymptomSync SQL, schema contracts, and reminder plumbing safely. Use when tasks touch supabase/, database/, database/migrations/, SQL functions, cron/reminder logic, user_notifications behavior, mirrored schema maintenance, or frontend code…

Workflow for keeping SymptomSync's checked-in docs aligned with implementation. Use when changes alter behavior described in README.md, ARCHITECTURE.md, DEPLOYMENTS.md, docs/, jenkins/README.md, or devops/runbooks/, or when a task is specifically about…

Guide for making safe changes to SymptomSync infrastructure, CI/CD, deployment, and operational behavior. Use when tasks touch aws/, ansible/, jenkins/, devops/, Dockerfile, .devcontainer/, or .github/workflows/ci.yml, especially for CDK stack changes,…

Repo-specific review workflow for SymptomSync. Use when reviewing code, plans, or diffs across frontend, SQL, AI service, infrastructure, or CI/CD so the review reflects this repository's real failure modes such as mirrored SQL drift, weak frontend test…

Guide for making safe, repo-specific changes in SymptomSync's Next.js frontend under web/. Use when tasks touch pages-router pages, React components, Supabase client flows, Gemini chat UX, charts, calendar behavior, uploads, auth screens, or frontend-facing…