forwward-teams

Use when designing system architecture, choosing databases, structuring projects, selecting tech stacks, designing APIs, planning caching strategies, or organizing a codebase for scale

Use when implementing features, writing fullstack code, shipping UI + API + DB changes, or any hands-on engineering work in TypeScript, Python, React, Next.js, FastAPI, or SQL

Use when making high-level business decisions — vision, OKRs, hiring, fundraising, resource allocation, pivots, or any strategic leadership question

Use when making architecture decisions, evaluating build-vs-buy, planning tech stack, prioritizing tech debt, writing PRDs, or needing strategic technical leadership

Use when writing SQL queries, building analytics dashboards, tracking metrics, designing data pipelines, or analyzing user behavior and product usage

Use when making UI/UX decisions, building components, choosing colors, layouts, typography, or reviewing any visual design — enforces anti-slop standards against generic AI aesthetics

Use when setting up CI/CD, Docker, deployment pipelines, monitoring, alerting, infrastructure, or debugging production issues

Use when modeling unit economics, calculating burn rate, building financial projections, pricing analysis, revenue forecasting, or any CFO-level financial decisions

Use when verifying code works — after feature work, before committing, before deploy, or any request to "verify", "check", or "make sure it works"

Use when designing viral loops, referral systems, growth mechanics, launch playbooks, or analyzing growth metrics for product-led growth

Use when drafting terms of service, privacy policies, contracts, IP assignments, open source licensing, or any legal document — asks about industry context and reviews existing docs before drafting

Use when analyzing patient records, clinical notes, medical PDFs, FHIR data, or advising on how to present medical data in health-tech products — OCR interpretation, clinical summarization, differential diagnosis support, drug interaction flags

Use when setting up a new AI agent from scratch — asks 10 discovery questions, configures the correct files for the target system, tests integrations, and implements security guardrails

Use when building landing pages, auditing conversion copy, writing email sequences, social posts, or any persuasive content that needs to resonate rather than direct. Triggers on requests involving ICP targeting, conversion optimization, landing page creation, copy audits, perception shifting, micro-compliance, or SEO-friendly persuasive writing.

Use when reviewing code for bugs, security issues, race conditions, N+1 queries, trust boundary violations, or any pre-merge quality check

Use when writing outreach sequences, preparing demos, handling objections, building CRM workflows, or any direct sales and customer acquisition activities

Use when handling authentication, authorization, encryption, HIPAA compliance, SOC 2, privacy policies, penetration testing, or any security and compliance concerns

Use when ready to release — creating branches, syncing, running final checks, pushing code, opening PRs, or automating any part of the release workflow

Use when a user first installs forwward-teams or starts a new project — onboards them, learns about their company, initializes the environment, and recommends which skills to use first

Use when defining target customers, building ICPs, researching competitors, crafting positioning, developing pricing, or running strategic discovery conversations

Use when migrating to another AI platform — exports all stored memories, context, preferences, and instructions so you can import them elsewhere

Use when orchestrating multi-agent teams for parallel work — feature dev, quality audits, research sprints, bug hunts, or any task needing 2+ agents working concurrently

Use when writing blog posts, X/Twitter threads, newsletters, or any founder-voice content — raw, specific, no fluff

2 hooks across 2 events