@zenrick/zenkit 0.0.0-stage → 0.5.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.claude-plugin/marketplace.json +19 -0
- package/.cursor-plugin/marketplace.json +22 -0
- package/INSTALL.md +73 -0
- package/LICENSE +202 -0
- package/NOTICE +5 -0
- package/README.md +69 -3
- package/TERMS.md +48 -0
- package/THIRD-PARTY-NOTICES.md +109 -0
- package/kit/agents/backend-specialist.md +263 -0
- package/kit/agents/code-archaeologist.md +106 -0
- package/kit/agents/database-architect.md +226 -0
- package/kit/agents/debugger.md +226 -0
- package/kit/agents/devops-engineer.md +242 -0
- package/kit/agents/documentation-writer.md +104 -0
- package/kit/agents/explorer-agent.md +73 -0
- package/kit/agents/frontend-specialist.md +593 -0
- package/kit/agents/game-developer.md +162 -0
- package/kit/agents/mobile-developer.md +377 -0
- package/kit/agents/orchestrator.md +489 -0
- package/kit/agents/penetration-tester.md +188 -0
- package/kit/agents/performance-optimizer.md +187 -0
- package/kit/agents/product-manager.md +112 -0
- package/kit/agents/product-owner.md +95 -0
- package/kit/agents/project-planner.md +409 -0
- package/kit/agents/qa-automation-engineer.md +103 -0
- package/kit/agents/security-auditor.md +170 -0
- package/kit/agents/seo-specialist.md +111 -0
- package/kit/agents/test-engineer.md +158 -0
- package/kit/bundles/agent-building.yaml +26 -0
- package/kit/bundles/backend-data.yaml +14 -0
- package/kit/bundles/base.yaml +10 -0
- package/kit/bundles/core.yaml +21 -0
- package/kit/bundles/kit-engenharia.yaml +8 -0
- package/kit/bundles/kit-lite.yaml +9 -0
- package/kit/bundles/security.yaml +11 -0
- package/kit/bundles/ship-run.yaml +16 -0
- package/kit/bundles/web-ui.yaml +18 -0
- package/kit/commands/docs.md +33 -0
- package/kit/commands/explain.md +41 -0
- package/kit/commands/fix.md +65 -0
- package/kit/commands/implement.md +35 -0
- package/kit/commands/refactor.md +59 -0
- package/kit/commands/review.md +55 -0
- package/kit/commands/test.md +63 -0
- package/kit/modules/bridge/rules/cross-ide-bridge.mdc +73 -0
- package/kit/modules/bridge/zenkit-layer.yaml +1 -0
- package/kit/modules/nexuscore/sections/convivencia.md +12 -0
- package/kit/modules/nexuscore/sections/memoria.md +9 -0
- package/kit/modules/nexuscore/skills/quadro-agentes/SKILL.md +186 -0
- package/kit/modules/nexuscore/zenkit-layer.yaml +1 -0
- package/kit/rules/ZENKIT.mdc +294 -0
- package/kit/rules/git.mdc +51 -0
- package/kit/rules/karpathy-guidelines.mdc +70 -0
- package/kit/rules/model-routing.mdc +89 -0
- package/kit/rules/security-headers.mdc +41 -0
- package/kit/rules/social-automation.mdc +69 -0
- package/kit/rules/toc.mdc +40 -0
- package/kit/skills/api-patterns/SKILL.md +95 -0
- package/kit/skills/api-patterns/api-style.md +42 -0
- package/kit/skills/api-patterns/auth.md +24 -0
- package/kit/skills/api-patterns/documentation.md +26 -0
- package/kit/skills/api-patterns/graphql.md +41 -0
- package/kit/skills/api-patterns/rate-limiting.md +31 -0
- package/kit/skills/api-patterns/references/backend/backend-api-design.md +495 -0
- package/kit/skills/api-patterns/references/backend/backend-architecture.md +454 -0
- package/kit/skills/api-patterns/references/backend/backend-authentication.md +338 -0
- package/kit/skills/api-patterns/references/backend/backend-code-quality.md +659 -0
- package/kit/skills/api-patterns/references/backend/backend-debugging.md +904 -0
- package/kit/skills/api-patterns/references/backend/backend-devops.md +494 -0
- package/kit/skills/api-patterns/references/backend/backend-mindset.md +387 -0
- package/kit/skills/api-patterns/references/backend/backend-performance.md +397 -0
- package/kit/skills/api-patterns/references/backend/backend-security.md +290 -0
- package/kit/skills/api-patterns/references/backend/backend-technologies.md +256 -0
- package/kit/skills/api-patterns/references/backend/backend-testing.md +429 -0
- package/kit/skills/api-patterns/response.md +37 -0
- package/kit/skills/api-patterns/rest.md +40 -0
- package/kit/skills/api-patterns/scripts/api_validator.py +211 -0
- package/kit/skills/api-patterns/security-testing.md +122 -0
- package/kit/skills/api-patterns/trpc.md +41 -0
- package/kit/skills/api-patterns/versioning.md +22 -0
- package/kit/skills/app-builder/SKILL.md +76 -0
- package/kit/skills/app-builder/agent-coordination.md +71 -0
- package/kit/skills/app-builder/feature-building.md +53 -0
- package/kit/skills/app-builder/project-detection.md +34 -0
- package/kit/skills/app-builder/scaffolding.md +118 -0
- package/kit/skills/app-builder/tech-stack.md +41 -0
- package/kit/skills/app-builder/templates/SKILL.md +39 -0
- package/kit/skills/app-builder/templates/astro-static/TEMPLATE.md +76 -0
- package/kit/skills/app-builder/templates/chrome-extension/TEMPLATE.md +92 -0
- package/kit/skills/app-builder/templates/cli-tool/TEMPLATE.md +88 -0
- package/kit/skills/app-builder/templates/electron-desktop/TEMPLATE.md +88 -0
- package/kit/skills/app-builder/templates/express-api/TEMPLATE.md +83 -0
- package/kit/skills/app-builder/templates/flutter-app/TEMPLATE.md +90 -0
- package/kit/skills/app-builder/templates/monorepo-turborepo/TEMPLATE.md +90 -0
- package/kit/skills/app-builder/templates/nextjs-fullstack/TEMPLATE.md +122 -0
- package/kit/skills/app-builder/templates/nextjs-saas/TEMPLATE.md +122 -0
- package/kit/skills/app-builder/templates/nextjs-static/TEMPLATE.md +169 -0
- package/kit/skills/app-builder/templates/nuxt-app/TEMPLATE.md +134 -0
- package/kit/skills/app-builder/templates/python-fastapi/TEMPLATE.md +83 -0
- package/kit/skills/app-builder/templates/react-native-app/TEMPLATE.md +119 -0
- package/kit/skills/architecture/SKILL.md +56 -0
- package/kit/skills/architecture/context-discovery.md +43 -0
- package/kit/skills/architecture/examples.md +94 -0
- package/kit/skills/architecture/pattern-selection.md +68 -0
- package/kit/skills/architecture/patterns-reference.md +50 -0
- package/kit/skills/architecture/trade-off-analysis.md +77 -0
- package/kit/skills/bash-linux/SKILL.md +203 -0
- package/kit/skills/batch-operations/SKILL.md +112 -0
- package/kit/skills/behavioral-modes/SKILL.md +255 -0
- package/kit/skills/brainstorming/SKILL.md +189 -0
- package/kit/skills/brainstorming/dynamic-questioning.md +350 -0
- package/kit/skills/brainstorming/references/problem-solving/attribution.md +69 -0
- package/kit/skills/brainstorming/references/problem-solving/collision-zone-thinking.md +79 -0
- package/kit/skills/brainstorming/references/problem-solving/inversion-exercise.md +91 -0
- package/kit/skills/brainstorming/references/problem-solving/meta-pattern-recognition.md +87 -0
- package/kit/skills/brainstorming/references/problem-solving/scale-game.md +95 -0
- package/kit/skills/brainstorming/references/problem-solving/simplification-cascades.md +80 -0
- package/kit/skills/brainstorming/references/problem-solving/when-stuck.md +72 -0
- package/kit/skills/claude-exec/SKILL.md +185 -0
- package/kit/skills/clean-code/SKILL.md +210 -0
- package/kit/skills/code-review-checklist/SKILL.md +115 -0
- package/kit/skills/code-review-graph/SKILL.md +50 -0
- package/kit/skills/code-review-graph/references/alternatives-comparison.md +12 -0
- package/kit/skills/code-review-graph/references/best-practices.md +9 -0
- package/kit/skills/code-review-graph/references/configuration.md +43 -0
- package/kit/skills/code-review-graph/references/core-workflows.md +61 -0
- package/kit/skills/code-review-graph/references/how-it-works-4-layers.md +20 -0
- package/kit/skills/code-review-graph/references/installation.md +67 -0
- package/kit/skills/code-review-graph/references/integration-with-zenkit.md +23 -0
- package/kit/skills/code-review-graph/references/known-limitations.md +13 -0
- package/kit/skills/code-review-graph/references/when-to-use-vs-when-to-skip.md +21 -0
- package/kit/skills/codex-exec/SKILL.md +161 -0
- package/kit/skills/context-compression/SKILL.md +145 -0
- package/kit/skills/coordinator-mode/SKILL.md +215 -0
- package/kit/skills/cursor-exec/SKILL.md +152 -0
- package/kit/skills/database-design/SKILL.md +53 -0
- package/kit/skills/database-design/database-selection.md +43 -0
- package/kit/skills/database-design/indexing.md +39 -0
- package/kit/skills/database-design/migrations.md +48 -0
- package/kit/skills/database-design/optimization.md +36 -0
- package/kit/skills/database-design/orm-selection.md +30 -0
- package/kit/skills/database-design/schema-design.md +56 -0
- package/kit/skills/database-design/scripts/schema_validator.py +172 -0
- package/kit/skills/deployment-procedures/SKILL.md +242 -0
- package/kit/skills/deprecation-and-migration/SKILL.md +149 -0
- package/kit/skills/documentation-templates/SKILL.md +195 -0
- package/kit/skills/entrega-com-agentes/SKILL.md +177 -0
- package/kit/skills/frontend-design/NOTICE.md +6 -0
- package/kit/skills/frontend-design/SKILL.md +456 -0
- package/kit/skills/frontend-design/animation-guide.md +331 -0
- package/kit/skills/frontend-design/color-system.md +311 -0
- package/kit/skills/frontend-design/decision-trees.md +418 -0
- package/kit/skills/frontend-design/motion-graphics.md +306 -0
- package/kit/skills/frontend-design/references/aesthetic/design-guideline-template.md +163 -0
- package/kit/skills/frontend-design/references/aesthetic/design-principles.md +62 -0
- package/kit/skills/frontend-design/references/aesthetic/design-resources.md +75 -0
- package/kit/skills/frontend-design/references/aesthetic/design-story-template.md +135 -0
- package/kit/skills/frontend-design/references/aesthetic/micro-interactions.md +53 -0
- package/kit/skills/frontend-design/references/aesthetic/storytelling-design.md +50 -0
- package/kit/skills/frontend-design/scripts/accessibility_checker.py +183 -0
- package/kit/skills/frontend-design/scripts/ux_audit.py +722 -0
- package/kit/skills/frontend-design/typography-system.md +345 -0
- package/kit/skills/frontend-design/ux-psychology.md +1116 -0
- package/kit/skills/frontend-design/visual-effects.md +383 -0
- package/kit/skills/game-development/2d-games/SKILL.md +119 -0
- package/kit/skills/game-development/3d-games/SKILL.md +135 -0
- package/kit/skills/game-development/SKILL.md +168 -0
- package/kit/skills/game-development/game-art/SKILL.md +185 -0
- package/kit/skills/game-development/game-audio/SKILL.md +190 -0
- package/kit/skills/game-development/game-design/SKILL.md +129 -0
- package/kit/skills/game-development/mobile-games/SKILL.md +108 -0
- package/kit/skills/game-development/multiplayer/SKILL.md +132 -0
- package/kit/skills/game-development/pc-games/SKILL.md +144 -0
- package/kit/skills/game-development/vr-ar/SKILL.md +123 -0
- package/kit/skills/game-development/web-games/SKILL.md +150 -0
- package/kit/skills/gemini-exec/SKILL.md +80 -0
- package/kit/skills/geo-fundamentals/SKILL.md +157 -0
- package/kit/skills/geo-fundamentals/scripts/geo_checker.py +289 -0
- package/kit/skills/git-worktrees/SKILL.md +107 -0
- package/kit/skills/i18n-localization/SKILL.md +145 -0
- package/kit/skills/i18n-localization/scripts/i18n_checker.py +241 -0
- package/kit/skills/intelligent-routing/SKILL.md +128 -0
- package/kit/skills/intelligent-routing/references/4-response-format.md +16 -0
- package/kit/skills/intelligent-routing/references/complexity-assessment.md +29 -0
- package/kit/skills/intelligent-routing/references/debug-intelligent-routing.md +9 -0
- package/kit/skills/intelligent-routing/references/debugging-agent-selection.md +7 -0
- package/kit/skills/intelligent-routing/references/domain-detection-rules.md +29 -0
- package/kit/skills/intelligent-routing/references/edge-cases.md +29 -0
- package/kit/skills/intelligent-routing/references/implementation-rules.md +35 -0
- package/kit/skills/intelligent-routing/references/integration-with-existing-workflows.md +21 -0
- package/kit/skills/intelligent-routing/references/performance-considerations.md +14 -0
- package/kit/skills/intelligent-routing/references/summary.md +16 -0
- package/kit/skills/intelligent-routing/references/testing-the-system.md +36 -0
- package/kit/skills/intelligent-routing/references/tier-0-automatic-analysis-always-active.md +27 -0
- package/kit/skills/intelligent-routing/references/user-education.md +12 -0
- package/kit/skills/karpathy-guidelines/SKILL.md +67 -0
- package/kit/skills/karpathy-guidelines/references/EXAMPLES.md +522 -0
- package/kit/skills/lint-and-validate/SKILL.md +46 -0
- package/kit/skills/lint-and-validate/scripts/lint_runner.py +184 -0
- package/kit/skills/lint-and-validate/scripts/type_coverage.py +173 -0
- package/kit/skills/mcp-atuacao/SKILL.md +238 -0
- package/kit/skills/mcp-builder/NOTICE.md +6 -0
- package/kit/skills/mcp-builder/SKILL.md +259 -0
- package/kit/skills/memory-system/SKILL.md +181 -0
- package/kit/skills/mobile-design/SKILL.md +395 -0
- package/kit/skills/mobile-design/decision-trees.md +516 -0
- package/kit/skills/mobile-design/mobile-backend.md +491 -0
- package/kit/skills/mobile-design/mobile-color-system.md +420 -0
- package/kit/skills/mobile-design/mobile-debugging.md +122 -0
- package/kit/skills/mobile-design/mobile-design-thinking.md +357 -0
- package/kit/skills/mobile-design/mobile-navigation.md +458 -0
- package/kit/skills/mobile-design/mobile-performance.md +767 -0
- package/kit/skills/mobile-design/mobile-testing.md +356 -0
- package/kit/skills/mobile-design/mobile-typography.md +433 -0
- package/kit/skills/mobile-design/platform-android.md +666 -0
- package/kit/skills/mobile-design/platform-ios.md +561 -0
- package/kit/skills/mobile-design/scripts/mobile_audit.py +670 -0
- package/kit/skills/mobile-design/touch-psychology.md +537 -0
- package/kit/skills/negocio-agente-conversa/SKILL.md +168 -0
- package/kit/skills/negocio-atendimento/SKILL.md +134 -0
- package/kit/skills/negocio-linguagem/SKILL.md +166 -0
- package/kit/skills/negocio-preco/SKILL.md +174 -0
- package/kit/skills/negocio-preco/scripts/preco.mjs +160 -0
- package/kit/skills/negocio-qualificacao/SKILL.md +140 -0
- package/kit/skills/nextjs-react-expert/1-async-eliminating-waterfalls.md +351 -0
- package/kit/skills/nextjs-react-expert/2-bundle-bundle-size-optimization.md +240 -0
- package/kit/skills/nextjs-react-expert/3-server-server-side-performance.md +490 -0
- package/kit/skills/nextjs-react-expert/4-client-client-side-data-fetching.md +264 -0
- package/kit/skills/nextjs-react-expert/5-rerender-re-render-optimization.md +581 -0
- package/kit/skills/nextjs-react-expert/6-rendering-rendering-performance.md +432 -0
- package/kit/skills/nextjs-react-expert/7-js-javascript-performance.md +684 -0
- package/kit/skills/nextjs-react-expert/8-advanced-advanced-patterns.md +150 -0
- package/kit/skills/nextjs-react-expert/9-cache-components.md +103 -0
- package/kit/skills/nextjs-react-expert/SKILL.md +308 -0
- package/kit/skills/nextjs-react-expert/resources/app-patterns/common-patterns.md +331 -0
- package/kit/skills/nextjs-react-expert/resources/app-patterns/complete-examples.md +872 -0
- package/kit/skills/nextjs-react-expert/resources/app-patterns/component-patterns.md +502 -0
- package/kit/skills/nextjs-react-expert/resources/app-patterns/data-fetching.md +767 -0
- package/kit/skills/nextjs-react-expert/resources/app-patterns/file-organization.md +502 -0
- package/kit/skills/nextjs-react-expert/resources/app-patterns/loading-and-error-states.md +501 -0
- package/kit/skills/nextjs-react-expert/resources/app-patterns/performance.md +406 -0
- package/kit/skills/nextjs-react-expert/resources/app-patterns/routing-guide.md +364 -0
- package/kit/skills/nextjs-react-expert/resources/app-patterns/styling-guide.md +428 -0
- package/kit/skills/nextjs-react-expert/resources/app-patterns/typescript-standards.md +418 -0
- package/kit/skills/nextjs-react-expert/scripts/convert_rules.py +222 -0
- package/kit/skills/nextjs-react-expert/scripts/react_performance_checker.py +252 -0
- package/kit/skills/nodejs-best-practices/SKILL.md +78 -0
- package/kit/skills/nodejs-best-practices/references/10-anti-patterns-to-avoid.md +21 -0
- package/kit/skills/nodejs-best-practices/references/11-decision-checklist.md +14 -0
- package/kit/skills/nodejs-best-practices/references/2-runtime-considerations-2025.md +36 -0
- package/kit/skills/nodejs-best-practices/references/3-architecture-principles.md +35 -0
- package/kit/skills/nodejs-best-practices/references/4-error-handling-principles.md +42 -0
- package/kit/skills/nodejs-best-practices/references/5-async-patterns-principles.md +35 -0
- package/kit/skills/nodejs-best-practices/references/6-validation-principles.md +29 -0
- package/kit/skills/nodejs-best-practices/references/7-security-principles.md +29 -0
- package/kit/skills/nodejs-best-practices/references/8-testing-principles.md +28 -0
- package/kit/skills/observability-and-instrumentation/SKILL.md +150 -0
- package/kit/skills/opencode-go-exec/SKILL.md +101 -0
- package/kit/skills/parallel-agents/SKILL.md +184 -0
- package/kit/skills/performance-profiling/SKILL.md +145 -0
- package/kit/skills/performance-profiling/scripts/lighthouse_audit.py +76 -0
- package/kit/skills/plan-writing/SKILL.md +213 -0
- package/kit/skills/powershell-windows/SKILL.md +196 -0
- package/kit/skills/provider-orchestration/SKILL.md +269 -0
- package/kit/skills/python-patterns/SKILL.md +80 -0
- package/kit/skills/python-patterns/references/10-decision-checklist.md +14 -0
- package/kit/skills/python-patterns/references/11-anti-patterns-to-avoid.md +20 -0
- package/kit/skills/python-patterns/references/2-async-vs-sync-decision.md +44 -0
- package/kit/skills/python-patterns/references/3-type-hints-strategy.md +56 -0
- package/kit/skills/python-patterns/references/4-project-structure-principles.md +56 -0
- package/kit/skills/python-patterns/references/5-django-principles-2025.md +40 -0
- package/kit/skills/python-patterns/references/6-fastapi-principles.md +50 -0
- package/kit/skills/python-patterns/references/7-background-tasks.md +31 -0
- package/kit/skills/python-patterns/references/8-error-handling-principles.md +29 -0
- package/kit/skills/python-patterns/references/9-testing-principles.md +37 -0
- package/kit/skills/red-team-tactics/SKILL.md +201 -0
- package/kit/skills/research/SKILL.md +166 -0
- package/kit/skills/rust-pro/SKILL.md +177 -0
- package/kit/skills/seo-fundamentals/SKILL.md +130 -0
- package/kit/skills/seo-fundamentals/scripts/seo_checker.py +219 -0
- package/kit/skills/sequential-thinking/.env.example +8 -0
- package/kit/skills/sequential-thinking/README.md +183 -0
- package/kit/skills/sequential-thinking/SKILL.md +95 -0
- package/kit/skills/sequential-thinking/package.json +31 -0
- package/kit/skills/sequential-thinking/references/advanced-strategies.md +79 -0
- package/kit/skills/sequential-thinking/references/advanced-techniques.md +76 -0
- package/kit/skills/sequential-thinking/references/core-patterns.md +95 -0
- package/kit/skills/sequential-thinking/references/examples-api.md +88 -0
- package/kit/skills/sequential-thinking/references/examples-architecture.md +94 -0
- package/kit/skills/sequential-thinking/references/examples-debug.md +90 -0
- package/kit/skills/sequential-thinking/scripts/format-thought.js +159 -0
- package/kit/skills/sequential-thinking/scripts/process-thought.js +236 -0
- package/kit/skills/server-management/SKILL.md +162 -0
- package/kit/skills/simplify-code/SKILL.md +133 -0
- package/kit/skills/skillify/SKILL.md +116 -0
- package/kit/skills/system-design-interview/SKILL.md +268 -0
- package/kit/skills/systematic-debugging/SKILL.md +110 -0
- package/kit/skills/tailwind-patterns/SKILL.md +283 -0
- package/kit/skills/tailwind-patterns/references/shadcn-ui/canvas-design-system.md +320 -0
- package/kit/skills/tailwind-patterns/references/shadcn-ui/shadcn-accessibility.md +471 -0
- package/kit/skills/tailwind-patterns/references/shadcn-ui/shadcn-components.md +424 -0
- package/kit/skills/tailwind-patterns/references/shadcn-ui/shadcn-theming.md +373 -0
- package/kit/skills/tailwind-patterns/references/shadcn-ui/tailwind-customization.md +483 -0
- package/kit/skills/tailwind-patterns/references/shadcn-ui/tailwind-responsive.md +382 -0
- package/kit/skills/tailwind-patterns/references/shadcn-ui/tailwind-utilities.md +455 -0
- package/kit/skills/tdd-workflow/SKILL.md +150 -0
- package/kit/skills/testing-patterns/SKILL.md +196 -0
- package/kit/skills/testing-patterns/scripts/test_runner.py +219 -0
- package/kit/skills/ui-ux-pro-max/SKILL.md +135 -0
- package/kit/skills/verify-changes/SKILL.md +125 -0
- package/kit/skills/vulnerability-scanner/SKILL.md +278 -0
- package/kit/skills/vulnerability-scanner/checklists.md +121 -0
- package/kit/skills/vulnerability-scanner/scripts/security_scan.py +458 -0
- package/kit/skills/web-design-guidelines/SKILL.md +58 -0
- package/kit/skills/webapp-testing/NOTICE.md +6 -0
- package/kit/skills/webapp-testing/SKILL.md +188 -0
- package/kit/skills/webapp-testing/scripts/playwright_runner.py +173 -0
- package/kit/workflows/brainstorm.md +113 -0
- package/kit/workflows/coordinate.md +72 -0
- package/kit/workflows/create.md +59 -0
- package/kit/workflows/debug.md +103 -0
- package/kit/workflows/deploy.md +176 -0
- package/kit/workflows/enhance.md +63 -0
- package/kit/workflows/orchestrate.md +237 -0
- package/kit/workflows/plan.md +89 -0
- package/kit/workflows/preview.md +81 -0
- package/kit/workflows/remember.md +67 -0
- package/kit/workflows/status.md +86 -0
- package/kit/workflows/test.md +144 -0
- package/kit/workflows/ui-ux-pro-max.md +296 -0
- package/kit/workflows/verify.md +72 -0
- package/licenses/Apache-2.0.txt +202 -0
- package/package.json +60 -6
- package/scripts/archive-codex-rollouts.ps1 +35 -0
- package/scripts/avaliar-vigilancia-mandato.mjs +38 -0
- package/scripts/bundle.mjs +170 -0
- package/scripts/check-deps.mjs +178 -0
- package/scripts/check-models.mjs +150 -0
- package/scripts/cli.mjs +313 -0
- package/scripts/content-checks.mjs +18 -0
- package/scripts/continuidade-mandato.mjs +47 -0
- package/scripts/discriminar-turno.mjs +191 -0
- package/scripts/doctor.mjs +611 -0
- package/scripts/generate.mjs +688 -0
- package/scripts/install.mjs +11 -0
- package/scripts/layer-remote.mjs +407 -0
- package/scripts/layers.mjs +208 -0
- package/scripts/marketplace.mjs +77 -0
- package/scripts/product.mjs +32 -0
- package/scripts/ruleset-core.mjs +68 -0
- package/scripts/social-hooks.mjs +293 -0
- package/scripts/social-pacer.mjs +219 -0
- package/scripts/validate-bundles.mjs +14 -0
- package/scripts/validate-skills.mjs +174 -0
- package/scripts/zenkit-daemon-task.cmd +3 -0
|
@@ -0,0 +1,189 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: brainstorming
|
|
3
|
+
description: Socratic questioning protocol + user communication. MANDATORY for complex requests, new features, or unclear requirements. Includes progress reporting and error handling.
|
|
4
|
+
when_to_use: "When exploring options before implementation, clarifying requirements, or when the user needs creative problem-solving. Use with /brainstorm workflow."
|
|
5
|
+
allowed-tools: Read, Glob, Grep
|
|
6
|
+
---
|
|
7
|
+
|
|
8
|
+
# Brainstorming & Communication Protocol
|
|
9
|
+
|
|
10
|
+
> **MANDATORY:** Use for complex/vague requests, new features, updates.
|
|
11
|
+
|
|
12
|
+
### Problem-solving references (cursor-kit merged)
|
|
13
|
+
|
|
14
|
+
| File | When to Read |
|
|
15
|
+
|------|--------------|
|
|
16
|
+
| `references/problem-solving/when-stuck.md` | Blocked or spiraling complexity |
|
|
17
|
+
| `references/problem-solving/simplification-cascades.md` | Reduce scope safely |
|
|
18
|
+
| `references/problem-solving/meta-pattern-recognition.md` | Recurring failure patterns |
|
|
19
|
+
| `references/problem-solving/scale-game.md` | Test ideas at extremes |
|
|
20
|
+
| `references/problem-solving/inversion-exercise.md` | Flip assumptions |
|
|
21
|
+
|
|
22
|
+
Structured step-by-step thinking: `@[skills/sequential-thinking]`.
|
|
23
|
+
|
|
24
|
+
---
|
|
25
|
+
|
|
26
|
+
## 🛑 SOCRATIC GATE (ENFORCEMENT)
|
|
27
|
+
|
|
28
|
+
### When to Trigger
|
|
29
|
+
|
|
30
|
+
| Pattern | Action |
|
|
31
|
+
|---------|--------|
|
|
32
|
+
| "Build/Create/Make [thing]" without details | 🛑 ASK 3 questions |
|
|
33
|
+
| Complex feature or architecture | 🛑 Clarify before implementing |
|
|
34
|
+
| Update/change request | 🛑 Confirm scope |
|
|
35
|
+
| Vague requirements | 🛑 Ask purpose, users, constraints |
|
|
36
|
+
|
|
37
|
+
### 🧠 Memory Check (2026.5.13 — Before Questioning)
|
|
38
|
+
|
|
39
|
+
> Before asking questions, check if past context exists:
|
|
40
|
+
|
|
41
|
+
```
|
|
42
|
+
0. CHECK MEMORY — Does .cursor/memory/MEMORY.md exist?
|
|
43
|
+
→ YES: Read index. Apply relevant past decisions silently.
|
|
44
|
+
Skip questions already answered in memory.
|
|
45
|
+
→ NO: Proceed with standard Socratic Gate.
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
### 🚫 MANDATORY: 3 Questions Before Implementation
|
|
49
|
+
|
|
50
|
+
1. **STOP** - Do NOT start coding
|
|
51
|
+
2. **CHECK** - Read `.cursor/memory/` for past context on this topic
|
|
52
|
+
3. **ASK** - Minimum 3 questions (skip any already answered via memory):
|
|
53
|
+
- 🎯 Purpose: What problem are you solving?
|
|
54
|
+
- 👥 Users: Who will use this?
|
|
55
|
+
- 📦 Scope: Must-have vs nice-to-have?
|
|
56
|
+
4. **WAIT** - Get response before proceeding
|
|
57
|
+
5. **SAVE** - After brainstorming, save key decisions: `/remember [decision]`
|
|
58
|
+
|
|
59
|
+
---
|
|
60
|
+
|
|
61
|
+
## 🧠 Dynamic Question Generation
|
|
62
|
+
|
|
63
|
+
**⛔ NEVER use static templates.** Read `dynamic-questioning.md` for principles.
|
|
64
|
+
|
|
65
|
+
### Core Principles
|
|
66
|
+
|
|
67
|
+
| Principle | Meaning |
|
|
68
|
+
|-----------|---------|
|
|
69
|
+
| **Questions Reveal Consequences** | Each question connects to an architectural decision |
|
|
70
|
+
| **Context Before Content** | Understand greenfield/feature/refactor/debug context first |
|
|
71
|
+
| **Minimum Viable Questions** | Each question must eliminate implementation paths |
|
|
72
|
+
| **Generate Data, Not Assumptions** | Don't guess—ask with trade-offs |
|
|
73
|
+
|
|
74
|
+
### Question Generation Process
|
|
75
|
+
|
|
76
|
+
```
|
|
77
|
+
1. Parse request → Extract domain, features, scale indicators
|
|
78
|
+
2. Identify decision points → Blocking vs. deferable
|
|
79
|
+
3. Generate questions → Priority: P0 (blocking) > P1 (high-leverage) > P2 (nice-to-have)
|
|
80
|
+
4. Format with trade-offs → What, Why, Options, Default
|
|
81
|
+
```
|
|
82
|
+
|
|
83
|
+
### Question Format (MANDATORY)
|
|
84
|
+
|
|
85
|
+
```markdown
|
|
86
|
+
### [PRIORITY] **[DECISION POINT]**
|
|
87
|
+
|
|
88
|
+
**Question:** [Clear question]
|
|
89
|
+
|
|
90
|
+
**Why This Matters:**
|
|
91
|
+
- [Architectural consequence]
|
|
92
|
+
- [Affects: cost/complexity/timeline/scale]
|
|
93
|
+
|
|
94
|
+
**Options:**
|
|
95
|
+
| Option | Pros | Cons | Best For |
|
|
96
|
+
|--------|------|------|----------|
|
|
97
|
+
| A | [+] | [-] | [Use case] |
|
|
98
|
+
|
|
99
|
+
**If Not Specified:** [Default + rationale]
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
**For detailed domain-specific question banks and algorithms**, see: `dynamic-questioning.md`
|
|
103
|
+
|
|
104
|
+
---
|
|
105
|
+
|
|
106
|
+
## Progress Reporting (PRINCIPLE-BASED)
|
|
107
|
+
|
|
108
|
+
**PRINCIPLE:** Transparency builds trust. Status must be visible and actionable.
|
|
109
|
+
|
|
110
|
+
### Status Board Format
|
|
111
|
+
|
|
112
|
+
| Agent | Status | Current Task | Progress |
|
|
113
|
+
|-------|--------|--------------|----------|
|
|
114
|
+
| [Agent Name] | ✅🔄⏳❌⚠️ | [Task description] | [% or count] |
|
|
115
|
+
|
|
116
|
+
### Status Icons
|
|
117
|
+
|
|
118
|
+
| Icon | Meaning | Usage |
|
|
119
|
+
|------|---------|-------|
|
|
120
|
+
| ✅ | Completed | Task finished successfully |
|
|
121
|
+
| 🔄 | Running | Currently executing |
|
|
122
|
+
| ⏳ | Waiting | Blocked, waiting for dependency |
|
|
123
|
+
| ❌ | Error | Failed, needs attention |
|
|
124
|
+
| ⚠️ | Warning | Potential issue, not blocking |
|
|
125
|
+
|
|
126
|
+
---
|
|
127
|
+
|
|
128
|
+
## Error Handling (PRINCIPLE-BASED)
|
|
129
|
+
|
|
130
|
+
**PRINCIPLE:** Errors are opportunities for clear communication.
|
|
131
|
+
|
|
132
|
+
### Error Response Pattern
|
|
133
|
+
|
|
134
|
+
```
|
|
135
|
+
1. Acknowledge the error
|
|
136
|
+
2. Explain what happened (user-friendly)
|
|
137
|
+
3. Offer specific solutions with trade-offs
|
|
138
|
+
4. Ask user to choose or provide alternative
|
|
139
|
+
```
|
|
140
|
+
|
|
141
|
+
### Error Categories
|
|
142
|
+
|
|
143
|
+
| Category | Response Strategy |
|
|
144
|
+
|----------|-------------------|
|
|
145
|
+
| **Port Conflict** | Offer alternative port or close existing |
|
|
146
|
+
| **Dependency Missing** | Auto-install or ask permission |
|
|
147
|
+
| **Build Failure** | Show specific error + suggested fix |
|
|
148
|
+
| **Unclear Error** | Ask for specifics: screenshot, console output |
|
|
149
|
+
|
|
150
|
+
---
|
|
151
|
+
|
|
152
|
+
## Completion Message (PRINCIPLE-BASED)
|
|
153
|
+
|
|
154
|
+
**PRINCIPLE:** Celebrate success, guide next steps.
|
|
155
|
+
|
|
156
|
+
### Completion Structure
|
|
157
|
+
|
|
158
|
+
```
|
|
159
|
+
1. Success confirmation (celebrate briefly)
|
|
160
|
+
2. Summary of what was done (concrete)
|
|
161
|
+
3. How to verify/test (actionable)
|
|
162
|
+
4. Next steps suggestion (proactive)
|
|
163
|
+
```
|
|
164
|
+
|
|
165
|
+
---
|
|
166
|
+
|
|
167
|
+
## Communication Principles
|
|
168
|
+
|
|
169
|
+
| Principle | Implementation |
|
|
170
|
+
|-----------|----------------|
|
|
171
|
+
| **Concise** | No unnecessary details, get to point |
|
|
172
|
+
| **Visual** | Use emojis (✅🔄⏳❌) for quick scanning |
|
|
173
|
+
| **Specific** | "~2 minutes" not "wait a bit" |
|
|
174
|
+
| **Alternatives** | Offer multiple paths when stuck |
|
|
175
|
+
| **Proactive** | Suggest next step after completion |
|
|
176
|
+
|
|
177
|
+
---
|
|
178
|
+
|
|
179
|
+
## Anti-Patterns (AVOID)
|
|
180
|
+
|
|
181
|
+
| Anti-Pattern | Why |
|
|
182
|
+
|--------------|-----|
|
|
183
|
+
| Jumping to solutions before understanding | Wastes time on wrong problem |
|
|
184
|
+
| Assuming requirements without asking | Creates wrong output |
|
|
185
|
+
| Over-engineering first version | Delays value delivery |
|
|
186
|
+
| Ignoring constraints | Creates unusable solutions |
|
|
187
|
+
| "I think" phrases | Uncertainty → Ask instead |
|
|
188
|
+
|
|
189
|
+
---
|
|
@@ -0,0 +1,350 @@
|
|
|
1
|
+
# Dynamic Question Generation
|
|
2
|
+
|
|
3
|
+
> **PRINCIPLE:** Questions are not about gathering data—they are about **revealing architectural consequences**.
|
|
4
|
+
>
|
|
5
|
+
> Every question must connect to a concrete implementation decision that affects cost, complexity, or timeline.
|
|
6
|
+
|
|
7
|
+
---
|
|
8
|
+
|
|
9
|
+
## 🧠 Core Principles
|
|
10
|
+
|
|
11
|
+
### 1. Questions Reveal Consequences
|
|
12
|
+
|
|
13
|
+
A good question is not "What color do you want?" but:
|
|
14
|
+
|
|
15
|
+
```markdown
|
|
16
|
+
❌ BAD: "What authentication method?"
|
|
17
|
+
✅ GOOD: "Should users sign up with email/password or social login?
|
|
18
|
+
|
|
19
|
+
Impact:
|
|
20
|
+
- Email/Pass → Need password reset, hashing, 2FA infrastructure
|
|
21
|
+
- Social → OAuth providers, user profile mapping, less control
|
|
22
|
+
|
|
23
|
+
Trade-off: Security vs. Development time vs. User friction"
|
|
24
|
+
```
|
|
25
|
+
|
|
26
|
+
### 2. Context Before Content
|
|
27
|
+
|
|
28
|
+
First understand **where** this request fits:
|
|
29
|
+
|
|
30
|
+
| Context | Question Focus |
|
|
31
|
+
|---------|----------------|
|
|
32
|
+
| **Greenfield** (new project) | Foundation decisions: stack, hosting, scale |
|
|
33
|
+
| **Feature Addition** | Integration points, existing patterns, breaking changes |
|
|
34
|
+
| **Refactor** | Why refactor? Performance? Maintainability? What's broken? |
|
|
35
|
+
| **Debug** | Symptoms → Root cause → Reproduction path |
|
|
36
|
+
|
|
37
|
+
### 3. Minimum Viable Questions
|
|
38
|
+
|
|
39
|
+
**PRINCIPLE:** Each question must eliminate a fork in the implementation road.
|
|
40
|
+
|
|
41
|
+
```
|
|
42
|
+
Before Question:
|
|
43
|
+
├── Path A: Do X (5 min)
|
|
44
|
+
├── Path B: Do Y (15 min)
|
|
45
|
+
└── Path C: Do Z (1 hour)
|
|
46
|
+
|
|
47
|
+
After Question:
|
|
48
|
+
└── Path Confirmed: Do X (5 min)
|
|
49
|
+
```
|
|
50
|
+
|
|
51
|
+
If a question doesn't reduce implementation paths → **DELETE IT**.
|
|
52
|
+
|
|
53
|
+
### 4. Questions Generate Data, Not Assumptions
|
|
54
|
+
|
|
55
|
+
```markdown
|
|
56
|
+
❌ ASSUMPTION: "User probably wants Stripe for payments"
|
|
57
|
+
✅ QUESTION: "Which payment provider fits your needs?
|
|
58
|
+
|
|
59
|
+
Stripe → Best documentation, 2.9% + $0.30, US-centric
|
|
60
|
+
LemonSqueezy → Merchant of Record, 5% + $0.50, global taxes
|
|
61
|
+
Paddle → Complex pricing, handles EU VAT, enterprise focus"
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
---
|
|
65
|
+
|
|
66
|
+
## 📋 Question Generation Algorithm
|
|
67
|
+
|
|
68
|
+
```
|
|
69
|
+
INPUT: User request + Context (greenfield/feature/refactor/debug)
|
|
70
|
+
│
|
|
71
|
+
├── STEP 1: Parse Request
|
|
72
|
+
│ ├── Extract domain (ecommerce, auth, realtime, cms, etc.)
|
|
73
|
+
│ ├── Extract features (explicit and implied)
|
|
74
|
+
│ └── Extract scale indicators (users, data volume, frequency)
|
|
75
|
+
│
|
|
76
|
+
├── STEP 2: Identify Decision Points
|
|
77
|
+
│ ├── What MUST be decided before coding? (blocking)
|
|
78
|
+
│ ├── What COULD be decided later? (deferable)
|
|
79
|
+
│ └── What has ARCHITECTURAL impact? (high-leverage)
|
|
80
|
+
│
|
|
81
|
+
├── STEP 3: Generate Questions (Priority Order)
|
|
82
|
+
│ ├── P0: Blocking decisions (cannot proceed without answer)
|
|
83
|
+
│ ├── P1: High-leverage (affects >30% of implementation)
|
|
84
|
+
│ ├── P2: Medium-leverage (affects specific features)
|
|
85
|
+
│ └── P3: Nice-to-have (edge cases, optimization)
|
|
86
|
+
│
|
|
87
|
+
└── STEP 4: Format Each Question
|
|
88
|
+
├── What: Clear question
|
|
89
|
+
├── Why: Impact on implementation
|
|
90
|
+
├── Options: Trade-offs (not just A vs B)
|
|
91
|
+
└── Default: What happens if user doesn't answer
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
---
|
|
95
|
+
|
|
96
|
+
## 🎯 Domain-Specific Question Banks
|
|
97
|
+
|
|
98
|
+
### E-Commerce
|
|
99
|
+
|
|
100
|
+
| Question | Why It Matters | Trade-offs |
|
|
101
|
+
|----------|----------------|------------|
|
|
102
|
+
| **Single or Multi-vendor?** | Multi-vendor → Commission logic, vendor dashboards, split payments | +Revenue, -Complexity |
|
|
103
|
+
| **Inventory Tracking?** | Needs stock tables, reservation logic, low-stock alerts | +Accuracy, -Development time |
|
|
104
|
+
| **Digital or Physical Products?** | Digital → Download links, no shipping | Physical → Shipping APIs, tracking |
|
|
105
|
+
| **Subscription or One-time?** | Subscription → Recurring billing, dunning, proration | +Revenue, -Complexity |
|
|
106
|
+
|
|
107
|
+
### Authentication
|
|
108
|
+
|
|
109
|
+
| Question | Why It Matters | Trade-offs |
|
|
110
|
+
|----------|----------------|------------|
|
|
111
|
+
| **Social Login Needed?** | OAuth providers vs. password reset infrastructure | +UX, -Control |
|
|
112
|
+
| **Role-Based Permissions?** | RBAC tables, policy enforcement, admin UI | +Security, -Development time |
|
|
113
|
+
| **2FA Required?** | TOTP/SMI infrastructure, backup codes, recovery flow | +Security, -UX friction |
|
|
114
|
+
| **Email Verification?** | Verification tokens, email service, resend logic | +Security, -Sign-up friction |
|
|
115
|
+
|
|
116
|
+
### Real-time
|
|
117
|
+
|
|
118
|
+
| Question | Why It Matters | Trade-offs |
|
|
119
|
+
|----------|----------------|------------|
|
|
120
|
+
| **WebSocket or Polling?** | WS → Server scaling, connection management | Polling → Simpler, higher latency |
|
|
121
|
+
| **Expected Concurrent Users?** | <100 → Single server, >1000 → Redis pub/sub, >10k → specialized infra | +Scale, -Complexity |
|
|
122
|
+
| **Message Persistence?** | History tables, storage costs, pagination | +UX, -Storage |
|
|
123
|
+
| **Ephemeral or Durable?** | Ephemeral → In-memory, Durable → Database write before emit | +Reliability, -Latency |
|
|
124
|
+
|
|
125
|
+
### Content/CMS
|
|
126
|
+
|
|
127
|
+
| Question | Why It Matters | Trade-offs |
|
|
128
|
+
|----------|----------------|------------|
|
|
129
|
+
| **Rich Text or Markdown?** | Rich Text → Sanitization, XSS risks | Markdown → Simple, no WYSIWYG |
|
|
130
|
+
| **Draft/Publish Workflow?** | Status field, scheduled jobs, versioning | +Control, -Complexity |
|
|
131
|
+
| **Media Handling?** | Upload endpoints, storage, optimization | +Features, -Development time |
|
|
132
|
+
| **Multi-language?** | i18n tables, translation UI, fallback logic | +Reach, -Complexity |
|
|
133
|
+
|
|
134
|
+
---
|
|
135
|
+
|
|
136
|
+
## 📐 Dynamic Question Template
|
|
137
|
+
|
|
138
|
+
```markdown
|
|
139
|
+
Based on your request for [DOMAIN] [FEATURE]:
|
|
140
|
+
|
|
141
|
+
## 🔴 CRITICAL (Blocking Decisions)
|
|
142
|
+
|
|
143
|
+
### 1. **[DECISION POINT]**
|
|
144
|
+
|
|
145
|
+
**Question:** [Clear, specific question]
|
|
146
|
+
|
|
147
|
+
**Why This Matters:**
|
|
148
|
+
- [Explain architectural consequence]
|
|
149
|
+
- [Affects: cost / complexity / timeline / scale]
|
|
150
|
+
|
|
151
|
+
**Options:**
|
|
152
|
+
| Option | Pros | Cons | Best For |
|
|
153
|
+
|--------|------|------|----------|
|
|
154
|
+
| A | [Advantage] | [Disadvantage] | [Use case] |
|
|
155
|
+
| B | [Advantage] | [Disadvantage] | [Use case] |
|
|
156
|
+
|
|
157
|
+
**If Not Specified:** [Default choice + rationale]
|
|
158
|
+
|
|
159
|
+
---
|
|
160
|
+
|
|
161
|
+
## 🟡 HIGH-LEVERAGE (Affects Implementation)
|
|
162
|
+
|
|
163
|
+
### 2. **[DECISION POINT]**
|
|
164
|
+
[Same format]
|
|
165
|
+
|
|
166
|
+
---
|
|
167
|
+
|
|
168
|
+
## 🟢 NICE-TO-HAVE (Edge Cases)
|
|
169
|
+
|
|
170
|
+
### 3. **[DECISION POINT]**
|
|
171
|
+
[Same format]
|
|
172
|
+
```
|
|
173
|
+
|
|
174
|
+
---
|
|
175
|
+
|
|
176
|
+
## 🔄 Iterative Questioning
|
|
177
|
+
|
|
178
|
+
### First Pass (3-5 Questions)
|
|
179
|
+
Focus on **blocking decisions**. Don't proceed without answers.
|
|
180
|
+
|
|
181
|
+
### Second Pass (After Initial Implementation)
|
|
182
|
+
As patterns emerge, ask:
|
|
183
|
+
- "This feature implies [X]. Should we handle [edge case] now or defer?"
|
|
184
|
+
- "We're using [Pattern A]. Should [Feature B] follow the same pattern?"
|
|
185
|
+
|
|
186
|
+
### Third Pass (Optimization)
|
|
187
|
+
When functionality works:
|
|
188
|
+
- "Performance bottleneck at [X]. Optimize now or acceptable for now?"
|
|
189
|
+
- "Refactor [Y] for maintainability or ship as-is?"
|
|
190
|
+
|
|
191
|
+
---
|
|
192
|
+
|
|
193
|
+
## 🎭 Example: Full Question Generation
|
|
194
|
+
|
|
195
|
+
```
|
|
196
|
+
USER REQUEST: "Build an Instagram clone"
|
|
197
|
+
|
|
198
|
+
STEP 1: Parse
|
|
199
|
+
├── Domain: Social Media
|
|
200
|
+
├── Features: Photo sharing, engagement (likes/comments), user profiles
|
|
201
|
+
├── Implied: Feed, following, authentication
|
|
202
|
+
└── Scale: Potentially high (social apps go viral)
|
|
203
|
+
|
|
204
|
+
STEP 2: Decision Points
|
|
205
|
+
├── Blocking: Storage strategy, authentication method, feed type
|
|
206
|
+
├── High-leverage: Real-time notifications, data model complexity
|
|
207
|
+
└── Deferable: Analytics, advanced search, reels/video
|
|
208
|
+
|
|
209
|
+
STEP 3: Generate Questions (Priority)
|
|
210
|
+
|
|
211
|
+
P0 (Blocking):
|
|
212
|
+
1. Storage Strategy → Affects architecture, cost, speed
|
|
213
|
+
2. Feed Algorithm → Affects database queries, complexity
|
|
214
|
+
3. Auth Method → Affects dev time, UX, security
|
|
215
|
+
|
|
216
|
+
P1 (High-leverage):
|
|
217
|
+
4. Real-time Notifications → WebSocket vs polling
|
|
218
|
+
5. Media Processing → Client-side vs server-side optimization
|
|
219
|
+
|
|
220
|
+
P2 (Deferable):
|
|
221
|
+
6. Story/Reels → Major feature creep, defer to v2
|
|
222
|
+
7. DM/Chat → Separate subsystem, defer to v2
|
|
223
|
+
|
|
224
|
+
STEP 4: Format Output
|
|
225
|
+
```
|
|
226
|
+
|
|
227
|
+
---
|
|
228
|
+
|
|
229
|
+
## 📊 Generated Output (Example)
|
|
230
|
+
|
|
231
|
+
```
|
|
232
|
+
Based on your Instagram clone request:
|
|
233
|
+
|
|
234
|
+
## 🔴 CRITICAL DECISIONS (Cannot Proceed Without Answers)
|
|
235
|
+
|
|
236
|
+
### 1. **Photo Storage Strategy**
|
|
237
|
+
|
|
238
|
+
**Question:** Where will user photos be stored and served?
|
|
239
|
+
|
|
240
|
+
**Why This Matters:**
|
|
241
|
+
- Affects: Monthly hosting costs, page load speed, CDN complexity
|
|
242
|
+
- High-volume social apps: 1000 users × 10 photos × 2MB = 20GB storage
|
|
243
|
+
|
|
244
|
+
**Options:**
|
|
245
|
+
| Option | Cost | Speed | Complexity | Best For |
|
|
246
|
+
|--------|------|-------|------------|----------|
|
|
247
|
+
| **Cloudinary** | $89/mo (25GB) | Fast (CDN) | Low | MVP, rapid launch |
|
|
248
|
+
| **AWS S3 + CloudFront** | $0.023/GB | Fast (CDN) | Medium | Production, cost-optimized |
|
|
249
|
+
| **Supabase Storage** | Free tier 1GB | Medium | Low | Small scale, simple |
|
|
250
|
+
| **Local Storage** | Server cost | Slow | Low | Development only |
|
|
251
|
+
|
|
252
|
+
**If Not Specified:** Cloudinary (balanced for MVP)
|
|
253
|
+
|
|
254
|
+
---
|
|
255
|
+
|
|
256
|
+
### 2. **Feed Algorithm Choice**
|
|
257
|
+
|
|
258
|
+
**Question:** How should the main feed work?
|
|
259
|
+
|
|
260
|
+
**Why This Matters:**
|
|
261
|
+
- Affects: Database query complexity, caching strategy, development time
|
|
262
|
+
- Algorithmic feeds require ML infrastructure, ranking signals
|
|
263
|
+
|
|
264
|
+
**Options:**
|
|
265
|
+
| Option | Complexity | Database Impact | Best For |
|
|
266
|
+
|--------|------------|-----------------|----------|
|
|
267
|
+
| **Chronological** | Low | Simple query | Early stage, transparency |
|
|
268
|
+
| **Follow-Only** | Medium | JOIN with pagination | Most social apps |
|
|
269
|
+
| **Algorithmic** | High | Pre-computed feed tables | Instagram competitor |
|
|
270
|
+
|
|
271
|
+
**If Not Specified:** Follow-Only (balanced for social app)
|
|
272
|
+
|
|
273
|
+
---
|
|
274
|
+
|
|
275
|
+
### 3. **Authentication Approach**
|
|
276
|
+
|
|
277
|
+
**Question:** How do users sign up and login?
|
|
278
|
+
|
|
279
|
+
**Why This Matters:**
|
|
280
|
+
- Affects: Development time (2-5 hours), security posture, UX friction
|
|
281
|
+
|
|
282
|
+
**Options:**
|
|
283
|
+
| Option | Dev Time | Security | UX | Best For |
|
|
284
|
+
|--------|----------|----------|-----|----------|
|
|
285
|
+
| **Email/Password** | 4-5 hrs | High (if 2FA) | Medium | Full control needed |
|
|
286
|
+
| **Social Only** | 1-2 hrs | Provider-dependent | Smooth | B2C, rapid launch |
|
|
287
|
+
| **Magic Link** | 2-3 hrs | Medium | Very smooth | Security-focused |
|
|
288
|
+
| **Clerk/Auth0** | 1 hr | High | Smooth | Fastest to market |
|
|
289
|
+
|
|
290
|
+
**If Not Specified:** Clerk (fastest for MVP)
|
|
291
|
+
|
|
292
|
+
---
|
|
293
|
+
|
|
294
|
+
## 🟡 HIGH-LEVERAGE (Affects Architecture)
|
|
295
|
+
|
|
296
|
+
### 4. **Real-time Notifications**
|
|
297
|
+
|
|
298
|
+
**Question:** Do users need instant notifications for likes/comments?
|
|
299
|
+
|
|
300
|
+
**Why This Matters:**
|
|
301
|
+
- WebSocket adds infrastructure complexity (Redis pub/sub for scaling)
|
|
302
|
+
- Polling is simpler but higher latency
|
|
303
|
+
|
|
304
|
+
**Options:**
|
|
305
|
+
| Option | Complexity | Scale Cost | Best For |
|
|
306
|
+
|--------|------------|------------|----------|
|
|
307
|
+
| **WebSocket + Redis** | High | $10+/mo | >1000 concurrent users |
|
|
308
|
+
| **Polling (30s)** | Low | DB queries | <1000 users |
|
|
309
|
+
| **No Real-time** | None | None | MVP, validate first |
|
|
310
|
+
|
|
311
|
+
**If Not Specified:** Polling for MVP (defer WebSocket until validated)
|
|
312
|
+
|
|
313
|
+
---
|
|
314
|
+
|
|
315
|
+
## 🟢 NICE-TO-HAVE (Defer to v2)
|
|
316
|
+
|
|
317
|
+
### 5. **Video/Reels Support**
|
|
318
|
+
- Major complexity (video processing, streaming infrastructure)
|
|
319
|
+
- Recommendation: Launch with photos only, add video after validation
|
|
320
|
+
|
|
321
|
+
### 6. **Direct Messaging**
|
|
322
|
+
- Separate subsystem (chat infrastructure different from feed)
|
|
323
|
+
- Recommendation: Use Pusher/Stream for real-time or defer entirely
|
|
324
|
+
|
|
325
|
+
---
|
|
326
|
+
|
|
327
|
+
## 📋 Summary
|
|
328
|
+
|
|
329
|
+
| Decision | Recommendation | If Changed |
|
|
330
|
+
|----------|----------------|------------|
|
|
331
|
+
| Storage | Cloudinary | +3 hrs setup |
|
|
332
|
+
| Feed | Follow-only | +2 hrs query optimization |
|
|
333
|
+
| Auth | Clerk | -3 hrs dev time |
|
|
334
|
+
| Real-time | Polling | +5 hrs WebSocket setup |
|
|
335
|
+
| Video | Defer to v2 | N/A |
|
|
336
|
+
| DM | Defer to v2 | N/A |
|
|
337
|
+
|
|
338
|
+
**Total Estimated MVP Time:** 15-20 hours with recommendations above
|
|
339
|
+
```
|
|
340
|
+
|
|
341
|
+
---
|
|
342
|
+
|
|
343
|
+
## 🎯 Principles Recap
|
|
344
|
+
|
|
345
|
+
1. **Every question = Architectural decision** → Not data gathering
|
|
346
|
+
2. **Show trade-offs** → User understands consequences
|
|
347
|
+
3. **Prioritize blocking decisions** → Cannot proceed without
|
|
348
|
+
4. **Provide defaults** → If user doesn't answer, we proceed anyway
|
|
349
|
+
5. **Domain-aware** → Ecommerce questions ≠ Auth questions ≠ Real-time questions
|
|
350
|
+
6. **Iterative** → More questions as patterns emerge during implementation
|
|
@@ -0,0 +1,69 @@
|
|
|
1
|
+
# Problem-Solving Skills - Attribution
|
|
2
|
+
|
|
3
|
+
These skills were derived from agent patterns in the Microsoft Amplifier project.
|
|
4
|
+
|
|
5
|
+
## Source Repository
|
|
6
|
+
|
|
7
|
+
- **Name:** Amplifier
|
|
8
|
+
- **URL:** https://github.com/microsoft/amplifier
|
|
9
|
+
- **Commit:** 2adb63f858e7d760e188197c8e8d4c1ef721e2a6
|
|
10
|
+
- **Date:** 2025-10-10
|
|
11
|
+
|
|
12
|
+
## Skills Derived from Amplifier Agents
|
|
13
|
+
|
|
14
|
+
### From insight-synthesizer agent:
|
|
15
|
+
- **simplification-cascades** - Finding insights that eliminate multiple components
|
|
16
|
+
- **collision-zone-thinking** - Forcing unrelated concepts together for breakthroughs
|
|
17
|
+
- **meta-pattern-recognition** - Spotting patterns across 3+ domains
|
|
18
|
+
- **inversion-exercise** - Flipping assumptions to reveal alternatives
|
|
19
|
+
- **scale-game** - Testing at extremes to expose fundamental truths
|
|
20
|
+
|
|
21
|
+
### From ambiguity-guardian agent:
|
|
22
|
+
- **preserving-productive-tensions** - Preserving multiple valid approaches (in architecture skill)
|
|
23
|
+
|
|
24
|
+
### From knowledge-archaeologist agent:
|
|
25
|
+
- **tracing-knowledge-lineages** - Understanding how ideas evolved (in research skill)
|
|
26
|
+
|
|
27
|
+
### Dispatch pattern:
|
|
28
|
+
- **when-stuck** - Maps stuck-symptoms to appropriate technique
|
|
29
|
+
|
|
30
|
+
## What Was Adapted
|
|
31
|
+
|
|
32
|
+
The Amplifier agents are specialized long-lived agents with structured JSON output. These skills extract the core problem-solving techniques and adapt them as:
|
|
33
|
+
|
|
34
|
+
- **Scannable quick-reference guides** (~60-80 lines each)
|
|
35
|
+
- **Symptom-based discovery** via when_to_use descriptions
|
|
36
|
+
- **Immediate application** without special tooling
|
|
37
|
+
- **Composable patterns** through dispatch system
|
|
38
|
+
- **Progressive disclosure** via SKILL.md + references structure
|
|
39
|
+
|
|
40
|
+
## Core Insight
|
|
41
|
+
|
|
42
|
+
Agent capabilities are domain-agnostic patterns. Whether packaged as "amplifier agent" or "problem-solving skill", the underlying technique is the same.
|
|
43
|
+
|
|
44
|
+
We extracted the techniques and made them:
|
|
45
|
+
- Portable across contexts
|
|
46
|
+
- Immediately applicable
|
|
47
|
+
- Token-efficient through progressive disclosure
|
|
48
|
+
- Discoverable through symptom-matching
|
|
49
|
+
- Combinable for complex problems
|
|
50
|
+
|
|
51
|
+
## License
|
|
52
|
+
|
|
53
|
+
Original Amplifier project uses MIT License. These adapted skills maintain attribution and follow the same open spirit.
|
|
54
|
+
|
|
55
|
+
## Adaptation Notes
|
|
56
|
+
|
|
57
|
+
**Changes from original:**
|
|
58
|
+
- Converted from long-lived agent to scannable reference
|
|
59
|
+
- Added symptom-based dispatch system
|
|
60
|
+
- Removed JSON output requirements
|
|
61
|
+
- Focused on immediate application
|
|
62
|
+
- Added concrete examples
|
|
63
|
+
- Structured for progressive disclosure
|
|
64
|
+
|
|
65
|
+
**Preserved from original:**
|
|
66
|
+
- Core problem-solving techniques
|
|
67
|
+
- Recognition patterns
|
|
68
|
+
- Application processes
|
|
69
|
+
- Fundamental insights
|
|
@@ -0,0 +1,79 @@
|
|
|
1
|
+
# Collision-Zone Thinking
|
|
2
|
+
|
|
3
|
+
Force unrelated concepts together to discover emergent properties. "What if we treated X like Y?"
|
|
4
|
+
|
|
5
|
+
## Core Principle
|
|
6
|
+
|
|
7
|
+
Revolutionary insights from deliberate metaphor-mixing. Treat X like Y and see what emerges.
|
|
8
|
+
|
|
9
|
+
## When to Use
|
|
10
|
+
|
|
11
|
+
| Symptom | Action |
|
|
12
|
+
|---------|--------|
|
|
13
|
+
| Stuck in conventional thinking | Force wild domain collision |
|
|
14
|
+
| Solutions feel incremental | Need breakthrough, not optimization |
|
|
15
|
+
| "Tried everything in this domain" | Import concepts from elsewhere |
|
|
16
|
+
| Need innovation, not iteration | Deliberately mix unrelated ideas |
|
|
17
|
+
|
|
18
|
+
## Quick Reference Collisions
|
|
19
|
+
|
|
20
|
+
| Treat This | Like This | Discovers |
|
|
21
|
+
|------------|-----------|-----------|
|
|
22
|
+
| Code organization | DNA/genetics | Mutation testing, evolutionary algorithms |
|
|
23
|
+
| Service architecture | Lego bricks | Composable microservices, plug-and-play |
|
|
24
|
+
| Data management | Water flow | Streaming, data lakes, flow-based systems |
|
|
25
|
+
| Request handling | Postal mail | Message queues, async processing |
|
|
26
|
+
| Error handling | Circuit breakers | Fault isolation, graceful degradation |
|
|
27
|
+
|
|
28
|
+
## Process
|
|
29
|
+
|
|
30
|
+
1. **Pick two unrelated concepts** from different domains
|
|
31
|
+
2. **Force combination** - "What if we treated [A] like [B]?"
|
|
32
|
+
3. **Explore emergent properties** - What new capabilities appear?
|
|
33
|
+
4. **Test boundaries** - Where does the metaphor break?
|
|
34
|
+
5. **Extract insight** - What did we learn?
|
|
35
|
+
|
|
36
|
+
## Detailed Example
|
|
37
|
+
|
|
38
|
+
**Problem:** Complex distributed system with cascading failures
|
|
39
|
+
|
|
40
|
+
**Collision:** "What if we treated services like electrical circuits?"
|
|
41
|
+
|
|
42
|
+
**Emergent properties:**
|
|
43
|
+
- Circuit breakers (disconnect on overload)
|
|
44
|
+
- Fuses (one-time failure protection)
|
|
45
|
+
- Ground faults (error isolation)
|
|
46
|
+
- Load balancing (current distribution)
|
|
47
|
+
- Voltage regulation (rate limiting)
|
|
48
|
+
|
|
49
|
+
**Where it works:** Preventing cascade failures, fault isolation
|
|
50
|
+
|
|
51
|
+
**Where it breaks:** Circuits don't have retry logic, healing mechanisms
|
|
52
|
+
|
|
53
|
+
**Insight gained:** Failure isolation patterns from electrical engineering
|
|
54
|
+
|
|
55
|
+
## Best Source Domains
|
|
56
|
+
|
|
57
|
+
Rich domains for concept mining:
|
|
58
|
+
- **Physics** - Forces, thermodynamics, relativity
|
|
59
|
+
- **Biology** - Evolution, ecosystems, immune systems
|
|
60
|
+
- **Economics** - Markets, incentives, game theory
|
|
61
|
+
- **Psychology** - Cognition, behavior, motivation
|
|
62
|
+
- **Architecture** - Structure, flow, space utilization
|
|
63
|
+
|
|
64
|
+
## Red Flags
|
|
65
|
+
|
|
66
|
+
You need collision-zone thinking when:
|
|
67
|
+
- "I've tried everything in this domain"
|
|
68
|
+
- Solutions feel incremental, not breakthrough
|
|
69
|
+
- Stuck in conventional thinking
|
|
70
|
+
- Need innovation, not optimization
|
|
71
|
+
- "Standard approach isn't working"
|
|
72
|
+
|
|
73
|
+
## Remember
|
|
74
|
+
|
|
75
|
+
- Wild combinations often yield best insights
|
|
76
|
+
- Test metaphor boundaries rigorously
|
|
77
|
+
- Document even failed collisions (they teach)
|
|
78
|
+
- Breakthrough > incremental improvement
|
|
79
|
+
- Question: "What would [domain expert] do?"
|