From 067ac5c1d054267f31132d283e414f543bd2ca5b Mon Sep 17 00:00:00 2001 From: jason Date: Mon, 23 Mar 2026 15:20:00 -0500 Subject: [PATCH] Upload files to "hubs" --- hubs/brainstorming.md | 25 ++++++++++++++++++++ hubs/debugging.md | 27 ++++++++++++++++++++++ hubs/documentation.md | 26 +++++++++++++++++++++ hubs/marketing.md | 26 +++++++++++++++++++++ hubs/software-development.md | 44 ++++++++++++++++++++++++++++++++++++ 5 files changed, 148 insertions(+) create mode 100644 hubs/brainstorming.md create mode 100644 hubs/debugging.md create mode 100644 hubs/documentation.md create mode 100644 hubs/marketing.md create mode 100644 hubs/software-development.md diff --git a/hubs/brainstorming.md b/hubs/brainstorming.md new file mode 100644 index 0000000..cddbd41 --- /dev/null +++ b/hubs/brainstorming.md @@ -0,0 +1,25 @@ +# Brainstorming Hub + +Use this hub when the task is to generate options, explore solution space, compare directions, or turn rough ideas into structured next steps. + +If [DEPLOYMENT-PROFILE.md](../DEPLOYMENT-PROFILE.md) contains brainstorming defaults, apply those preferences before falling back to the generic routing in this hub. + +## When To Use + +- The user wants concepts, options, or strategic directions +- Requirements are early-stage and need shaping +- A promising idea needs to become a scoped plan +- The team wants alternatives before implementation + +## Skill Routing + +- [Ideation](../skills/brainstorming/ideation.md) for broad option generation and concept creation +- [Structured Brainstorming](../skills/brainstorming/structured-brainstorming.md) for narrowing, comparing, scoring, and turning ideas into action +- [Roadmap and Opportunity Prioritization](../skills/brainstorming/roadmap-opportunity-prioritization.md) for sequencing initiatives, balancing impact versus effort, and choosing what should happen next + +## Common Combinations + +- Product concepting: ideation + messaging/positioning +- Solution design: ideation + structured brainstorming + repository exploration +- From ideas to build plan: structured brainstorming + feature implementation + test strategy +- Long-range planning: roadmap and opportunity prioritization + maintenance and technical debt planning + architecture and system design diff --git a/hubs/debugging.md b/hubs/debugging.md new file mode 100644 index 0000000..06c9922 --- /dev/null +++ b/hubs/debugging.md @@ -0,0 +1,27 @@ +# Debugging Hub + +Use this hub for work that begins with a defect, regression, failing test, production issue, or confusing system behavior. + +If [DEPLOYMENT-PROFILE.md](../DEPLOYMENT-PROFILE.md) contains debugging defaults, apply those preferences before falling back to the generic routing in this hub. + +## When To Use + +- A test is failing and the cause is unclear +- A user-reported bug needs reproduction and triage +- The system behaves inconsistently across environments or inputs +- A suspected regression needs careful isolation + +## Start With + +- [Bug Triage](../skills/debugging/bug-triage.md) to define the problem, impact, environment, and reproduction path +- [Debugging Workflow](../skills/debugging/debugging-workflow.md) to isolate root cause and verify a fix + +## Combine With + +- [API and Backend Work](../skills/software/api-backend.md) when the issue is server-side or data-related +- [Frontend UI Implementation](../skills/software/frontend-ui-implementation.md) when the issue is client-side or interaction-related +- [Test Strategy](../skills/software/test-strategy.md) when the fix needs coverage +- [Release and Change Summary](../skills/software/release-change-summary.md) when the resolution should be communicated clearly +- [Incident Response and Stabilization](../skills/debugging/incident-response-stabilization.md) when the issue is live, user-impacting, or needs temporary containment before a full fix +- [Observability and Operability](../skills/software/observability-operability.md) when logs, metrics, traces, or alerting gaps block diagnosis +- [Performance Optimization](../skills/software/performance-optimization.md) when the problem is latency, throughput, memory, or rendering related diff --git a/hubs/documentation.md b/hubs/documentation.md new file mode 100644 index 0000000..557cd06 --- /dev/null +++ b/hubs/documentation.md @@ -0,0 +1,26 @@ +# Documentation Hub + +Use this hub when the task changes how people understand, adopt, operate, or maintain the product. + +If [DEPLOYMENT-PROFILE.md](../DEPLOYMENT-PROFILE.md) contains documentation defaults, apply those preferences before falling back to the generic routing in this hub. + +## When To Use + +- Write or update technical documentation +- Improve onboarding or contributor guidance +- Create release notes or change summaries +- Align docs with code or product changes + +## Skill Routing + +- [Architecture Decision Records](../skills/documentation/architecture-decision-records.md) for capturing meaningful technical choices, tradeoffs, and why a direction was selected +- [Technical Documentation](../skills/documentation/technical-docs.md) for architecture, APIs, workflows, operational guidance, and usage docs +- [Onboarding Documentation](../skills/documentation/onboarding-docs.md) for setup guides, contributor onboarding, first-run experience, and internal enablement +- [Release and Change Summary](../skills/software/release-change-summary.md) for release notes, changelog writing, and rollout explanations + +## Common Combinations + +- New feature: technical docs + release/change summary +- Developer experience improvement: onboarding docs + technical docs +- Product launch: release/change summary + messaging/positioning + marketing content +- Long-lived architecture change: architecture and system design + architecture decision records + technical docs diff --git a/hubs/marketing.md b/hubs/marketing.md new file mode 100644 index 0000000..26472b2 --- /dev/null +++ b/hubs/marketing.md @@ -0,0 +1,26 @@ +# Marketing Hub + +Use this hub for external-facing product language, launch assets, positioning, and persuasive communication. + +If [DEPLOYMENT-PROFILE.md](../DEPLOYMENT-PROFILE.md) contains marketing defaults, apply those preferences before falling back to the generic routing in this hub. + +## When To Use + +- Draft launch messaging or feature announcements +- Improve website or product marketing copy +- Clarify product differentiation and audience fit +- Create marketing assets tied to engineering or product changes + +## Skill Routing + +- [Product Copy](../skills/marketing/product-copy.md) for UI-adjacent language, concise product text, and conversion-oriented wording +- [Marketing Content](../skills/marketing/marketing-content.md) for launch posts, feature pages, emails, social copy, and content drafts +- [Messaging and Positioning](../skills/marketing/messaging-positioning.md) for audience, value proposition, differentiation, and narrative framing +- [Content Strategy and SEO](../skills/marketing/content-strategy-seo.md) for durable organic content, search intent alignment, and content planning + +## Common Combinations + +- Feature launch: messaging/positioning + marketing content + release/change summary +- Landing page refresh: product copy + messaging/positioning + UX review +- Developer tool announcement: marketing content + technical docs + messaging/positioning +- Evergreen growth work: content strategy and SEO + messaging/positioning + technical docs diff --git a/hubs/software-development.md b/hubs/software-development.md new file mode 100644 index 0000000..da82bea --- /dev/null +++ b/hubs/software-development.md @@ -0,0 +1,44 @@ +# Software Development Hub + +Use this hub for implementation-focused software work: features, refactors, code review, tests, backend changes, frontend changes, and release communication tied to engineering output. + +If [DEPLOYMENT-PROFILE.md](../DEPLOYMENT-PROFILE.md) contains software defaults, apply those preferences before falling back to the generic routing in this hub. + +## When To Use + +- Build or modify product functionality +- Improve maintainability or architecture +- Review existing code for bugs, regressions, or missing tests +- Plan or add verification coverage +- Explore an unfamiliar codebase before changing it + +## Start With + +- [Repository Exploration](../skills/software/repo-exploration.md) for unfamiliar codebases or vague requests +- [Feature Implementation](../skills/software/feature-implementation.md) for net-new behavior or substantial changes + +## Skill Routing + +- [Architecture and System Design](../skills/software/architecture-system-design.md) for major system changes, design tradeoffs, and long-lived technical direction +- [Refactoring](../skills/software/refactoring.md) for structure improvements without intended behavior changes +- [Code Review](../skills/software/code-review.md) for finding bugs, regressions, risky assumptions, and missing coverage +- [Test Strategy](../skills/software/test-strategy.md) for designing, expanding, or evaluating verification +- [API and Backend Work](../skills/software/api-backend.md) for services, storage, schema, integration, and server-side logic +- [Database Migrations and Data Evolution](../skills/software/database-migrations.md) for schema changes, backfills, compatibility windows, and rollout-safe data transitions +- [Dependency Lifecycle Management](../skills/software/dependency-lifecycle.md) for upgrades, dependency risk reduction, and ecosystem maintenance +- [Performance Optimization](../skills/software/performance-optimization.md) for latency, throughput, rendering, and resource-efficiency work +- [Security Review and Hardening](../skills/software/security-review-hardening.md) for auth, validation, secrets, exposure, and abuse resistance concerns +- [Observability and Operability](../skills/software/observability-operability.md) for logging, metrics, traces, alerts, and operational readiness +- [Maintenance and Technical Debt Planning](../skills/software/maintenance-technical-debt.md) for long-horizon cleanup, risk reduction, and sequencing work +- [Frontend UI Implementation](../skills/software/frontend-ui-implementation.md) for interfaces, interaction logic, and client-side UX execution +- [Release and Change Summary](../skills/software/release-change-summary.md) for release notes, summaries, migration notes, and rollout communication + +## Common Combinations + +- New feature: repository exploration + feature implementation + test strategy + technical docs +- Backend bug fix: bug triage + debugging workflow + API and backend work + release/change summary +- UI feature: feature implementation + frontend UI implementation + UX review + product copy +- PR review: code review + test strategy +- Platform change: architecture and system design + API/backend work + observability and operability + technical docs +- Risky upgrade: dependency lifecycle management + test strategy + release/change summary +- Data model change: architecture and system design + database migrations and data evolution + API/backend work