athola/claude-night-market
52 skills · 3,409 total installs
$npx skills add athola/claude-night-marketSkillInstalls
project-brainstormingGuides project ideation via Socratic questioning to produce a validated brief. Use before specification when requirements are unclear.skills-evalEvaluate Claude skill quality through auditing. Use when reviewing or auditing skills.methodology-curatorSurface expert frameworks. Use when creating or evaluating skills, hooks, or agents.precommit-setupConfigures pre-commit hooks for linting, type checking, formatting, and testing. Use when setting up a new project or adding quality gates to an existing one.architecture-paradigmsSelects and routes to the right architecture paradigm. Use when choosing patterns for a new system or comparing trade-offs before making architecture decisions.architecture-paradigm-modular-monolithApplies modular monolith with enforced internal boundaries. Use when teams want service-level autonomy without distributed system overhead.makefile-generationGenerates Makefiles with testing, linting, formatting, and automation targets. Use when starting a project or standardizing build automation.subagent-testingTest skills via TDD in fresh subagents. Use when validating behavior or preventing bias.modular-skillsBuild composable skill modules with hub-and-spoke loading. Use when token budget is tight.skill-authoringGuide creating Claude Code skills with TDD and persuasion principles. Use for new skill development.architecture-paradigm-microkernelApplies microkernel architecture with minimal core and plugin extensibility. Use when building platforms where third parties extend core functionality.hook-authoringGuide creating Claude Code hooks with security-first design. Use for validation and enforcement.mission-orchestratorOrchestrates full project lifecycle by auto-detecting state and routing to the correct phase. Use when starting or resuming a project mid-workflow.architecture-paradigm-layeredApplies layered n-tier architecture with enforced boundaries. Use when designing moderate systems needing clear presentation, domain, and persistence layers.architecture-paradigm-microservicesApplies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.architecture-paradigm-cqrs-esApplies CQRS and Event Sourcing for read/write separation and audit trails. Use when designing systems with complex domain logic or full state-change history.architecture-paradigm-hexagonalApplies hexagonal architecture isolating domain from infrastructure. Use when designing systems where testability and port/adapter separation are priorities.architecture-paradigm-serverlessApplies serverless FaaS patterns for event-driven workloads. Use when designing bursty workloads with minimal infrastructure and pay-per-execution cost model.architecture-aware-initSelects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.architecture-paradigm-event-drivenApplies event-driven async messaging to decouple producers and consumers. Use when designing real-time or multi-subscriber systems needing loose coupling.architecture-paradigm-client-serverApplies client-server architecture for web/mobile apps. Use when designing systems with centralized backend services, trust boundaries, or offline-first sync.architecture-paradigm-service-basedApplies coarse-grained service architecture for deployment independence. Use when independent deployment is needed but shared databases rule out microservices.architecture-paradigm-functional-coreApplies Functional Core, Imperative Shell to isolate logic from side effects. Use when business logic is entangled with I/O or unit tests are slow and brittle.escalation-governanceAssess whether to escalate models. Use when evaluating reasoning depth.rules-evalEvaluate Claude Code rules in .claude/rules/. Use for frontmatter, globs, and quality audits.shared-patternsProvide reusable patterns for validation, error handling, scaffolding. Use for skill consistency.architecture-paradigm-space-basedApplies data-grid architecture for high-traffic stateful workloads. Use when a single database cannot scale and in-memory partitioning is needed.hooks-evalEvaluate hook security, performance, and SDK compliance. Use for audits.architecture-paradigm-pipelineApplies pipes-and-filters for sequential data transformations. Use when data flows through discrete stages like ETL, streaming analytics, or CI/CD pipelines.metacognitive-self-modAnalyze and improve the improvement process. Use for detecting regressions and meta-optimization.plugin-reviewReview plugin quality with tiered checks and dependency scoping. Use for PR and pre-release audits.dorodangoPolishes working code through successive quality passes in fresh subagents. Use after tests pass when code needs multi-dimension refinement before release.friction-detectorDetect friction signals; graduate patterns into rules. Use for session retrospectives.skill-graph-auditAudit Skill() refs; detect hubs, isolates, and dangling targets. Use when auditing skills.hook-scope-guideSelect hook scope (plugin, project, global) by audience. Use when authoring a hook.architecture-paradigm-domain-drivenModels a business in its own language. Use when the domain has real business rules to capture.claude-code-plugin-referenceExplain plugin, skill, command, agent, and hook mechanics used here. Use when authoring or debugging plugins. Do not use for ops; use night-market-operations.development-workflowDetailed development workflow with modular patterns for git, review, testing, and deployment.night-market-architecture-contractStates load-bearing decisions, invariants, and weak points. Use when judging a design change. Do not use for gating; use night-market-change-control.night-market-build-and-envRebuild the dev environment: uv, Python tiers, pins, traps. Use when onboarding or toolchain breaks. Do not use for daily commands; use night-market-operations.night-market-change-controlClassify, gate, and review changes. Use when landing a PR, releasing, or amending rules. Do not use for failure triage; use night-market-debugging-playbook.night-market-collective-memorySearch and record project memory (Discussions, journal, ADRs). Use before re-investigating anything. Do not use for settled battles; see failure-archaeology.night-market-completion-integrity-campaignBind loop 'done' to unfakeable gates. Use to harden egregore/herald loops or promote completion_integrity. Not for QA gates; use night-market-validation-and-qa.night-market-config-catalogCatalog every config axis, its defaults and guards. Use when adding or auditing configuration. Do not use for running gates; use night-market-operations.night-market-debugging-playbookTriage night-market failures by symptom (hooks, CI, tests). Use when a check fails unexpectedly. Do not use for routine gates; use night-market-operations.night-market-diagnostics-toolkitRun and interpret repo diagnostic scripts (ratchets, validators, token stats). Use when measuring health. Do not use to run tests; use night-market-operations.night-market-docs-and-writingMaintain docs of record, ADRs, changelog, and house style. Use when writing repo docs. Do not use for release steps; use night-market-operations instead.night-market-failure-archaeologyChronicles settled battles, reverts, and dead ends. Use when a fix echoes a past failure. Do not use for live triage; use night-market-debugging-playbook.night-market-operationsRun and ship this repo: make targets, artifacts, release runbook. Use when testing, linting, or releasing. Do not use for setup; use night-market-build-and-env.night-market-research-frontierMap open problems where this repo can advance SOTA. Use when scoping research. Do not use to run the campaign; use night-market-completion-integrity-campaign.night-market-research-methodologyTurn hunches into accepted results: worthiness score, evidence bar, research-to-rules. Use when vetting ideas. Not for QA; use night-market-validation-and-qa.night-market-validation-and-qaEnforce evidence bar, coverage gates, and regression guards. Use when adding tests or claiming done. Do not use to run suites; use night-market-operations.