blendai-issue-tagging
BlendAI Issue Tagging
Overview
Every issue gets two types of tags in Notion:
- Domain - Which product area(s) (Chat, Billing, Workflow Builder, etc.)
- Layer - Where in the technical stack (UI/UX, API/Backend, Database, etc.)
Multiple tags allowed - Assign all that apply based on task scope.
Quick Reference
Domains (25)
| Domain | Scope |
|---|---|
| Chat | Prompt area, messages, comparison mode, voice chat, chat UX |
| Memory | Memory extraction, follow-ups, saved context, recall |
| Personalization | User profile, preferences, custom behavior, adaptive AI |
| Projects | Project-scoped workspaces, attached context |
| Knowledge Base | Stored files, indexed content, persistent retrieval |
| AI Models | Model catalog, providers, model pricing, capabilities |
| Routing | Auto model selection, dispatchers, tool selection logic |
| Search | Web search, deep research, retrieval, query generation |
| Workflow Builder | Canvas, nodes, handles, templates, editor |
| Workflow Execution | Runs, queues, resumable jobs, streaming state |
| Workflow Sharing | Publish, marketplace, fork, revenue sharing |
| Smart Notes | Bookmark product, note UI, note retrieval |
| Capture | Share sheet, WhatsApp, OCR, transcription, ingestion |
| Billing | Credits, charges, Stripe mechanics |
| Pricing | Plans, tiers, feature gating, pricing page logic |
| Monetization | Discounts, affiliate, payouts, profit-share |
| Accounts | User lifecycle, onboarding, roles |
| Auth | Login, signup, permissions, access control |
| Settings | User preferences, app configuration |
| Support | Support chat, support tickets, founder messaging |
| Feedback | Feature requests, voting, changelog asks |
| Analytics | Dashboards, metrics, reporting |
| Internal Ops | Admin tools, maintenance surfaces, internal workflows |
| Growth Site | Landing page, marketing site, conversion pages |
| Content | Blog, outreach, SEO pages, marketing content ops |
Layers (5)
| Layer | Scope |
|---|---|
| UI/UX | Components, styling, interactions, accessibility, responsive design |
| API/Backend | Endpoints, business logic, validation, middleware, server code |
| Database | Schema, migrations, queries, indexes, data modeling |
| Integrations | External APIs, webhooks, third-party services, OAuth |
| Reliability | Performance, caching, error handling, monitoring, scaling |
Tagging Rules
- Assign all relevant Domains - Tag every product area the issue touches
- Assign all relevant Layers - Tag every technical layer involved
- Use Notion tags column - Add as tags (e.g.,
Chat,Memory,UI/UX,Database)
Examples
| Issue | Domains | Layers |
|---|---|---|
| "Chat input loses focus on mobile" | Chat | UI/UX |
| "Chat memory not persisting across sessions" | Chat, Memory | API/Backend, Database |
| "Stripe webhook not updating credits" | Billing | Integrations, API/Backend |
| "Full-stack workflow marketplace MVP" | Workflow Sharing, Monetization | UI/UX, API/Backend, Database |
| "Model selection dropdown slow + API timeout" | AI Models, Routing | UI/UX, API/Backend, Reliability |
Common Mistakes
| Mistake | Fix |
|---|---|
| Tagging only one Domain when multiple apply | Read scope carefully - tag all affected areas |
| Confusing Routing vs AI Models | Routing = selection logic; AI Models = catalog/pricing |
| Confusing Billing vs Pricing vs Monetization | Billing = Stripe/charges; Pricing = tiers/gates; Monetization = affiliate/payouts |
| Missing Reliability on perf issues | Any performance/scaling work needs Reliability tag |
More from marclelamy/skills
builder-review-loop
Use when one agent is implementing code and another agent must review the resulting changes, compare the summary against the actual files, decide whether to fix now or move on, and write the next tightly scoped prompt with context handoff guidance.
10code-commenting
Code commenting conventions for TypeScript/React projects. Use when adding comments to new files, reviewing uncommented code, or when user asks to document/comment code. Covers file headers, type annotations, function docs, inline comments, and what NOT to comment.
9frontend-design
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
9find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
9marketing-ideas
When the user needs marketing ideas, inspiration, or strategies for their SaaS or software product. Also use when the user asks for 'marketing ideas,' 'growth ideas,' 'how to market,' 'marketing strategies,' 'marketing tactics,' 'ways to promote,' 'ideas to grow,' 'what else can I try,' 'I don't know how to market this,' 'brainstorm marketing,' or 'what marketing should I do.' Use this as a starting point whenever someone is stuck or looking for inspiration on how to grow. For specific channel execution, see the relevant skill (paid-ads, social-content, email-sequence, etc.).
8tdd
Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.
8