Help us improve
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
Share bugs, ideas, or general feedback.
By fyrsmithlabs
Claude Code plugins for fyrsmithlabs project standards and workflows. Includes YAGNI/KISS enforcement, git-repo-standards, git-workflows with multi-agent consensus review, and GitHub planning integration.
npx claudepluginhub fyrsmithlabs/marketplace --plugin fs-devUse when starting a new app idea, exploring product concepts, or doing market research. Reads existing specs, conducts competitor analysis, and helps flesh out the app idea with differentiation strategies. Say "I have an app idea", "interview me about this product", or "help me differentiate from competitors".
Use when designing a feature, planning implementation, exploring approaches, or needing to think through a change before coding. Runs an interactive interview to understand requirements, assess complexity, explore alternatives, and create GitHub Issues. Say "let's brainstorm", "help me design", or "plan this feature".
Use when reviewing competitor analysis results, getting a quick market overview, or summarizing competitive landscape from previous app-interview sessions. Generates executive summary directly to terminal. Say "summarize competitors", "show competitive analysis", or "what did we learn about the market?".
Run a multi-agent consensus code review. Dispatches 5+ parallel agents and synthesizes findings. All agents have veto power unless --ignore-vetos is set.
Use when auditing codebase quality, finding security issues, identifying tech debt, checking test coverage, or scanning for improvements. Runs autonomous analysis across security, quality, performance, and documentation. Say "analyze this codebase", "find issues", "audit security", or "check code quality".
Code quality analysis agent for multi-agent consensus review. No veto power. Analyzes logic errors, test coverage gaps, cyclomatic complexity, code duplication, pattern violations, and error handling gaps.
Reviews technical documentation for accuracy, completeness, clarity, and adherence to best practices. Use when reviewing research reports, README files, API docs, or any technical writing. Has veto power for critical documentation issues.
Pre-session environment validation agent. Checks git config, branch state, tool availability, API token freshness, and project dependencies. Reports issues and suggests auto-remediation. Use as first step in any workflow or when encountering repeated configuration errors.
Go language specialist agent for multi-agent consensus review. Has VETO power on Go-specific issues. Analyzes gofmt compliance, naming conventions, error handling, control flow patterns, concurrency safety, interface design, and resource management using Effective Go principles.
Product owner agent for deep priority analysis, cross-project dependency mapping, and strategic recommendations. Use for complex prioritization decisions, historical pattern analysis, or platform-wide planning that goes beyond a simple standup.
Agent artifact placement conventions. Use when creating plans, tasks, research, reviews, brainstorms, or any agent-generated files. Ensures artifacts go to docs/.claude/ (gitignored) instead of polluting the repo.
Use when assessing task complexity, determining workflow depth, asking "how complex is this?", "should I use a worktree?", "is this a big change?", or sizing work before planning. Analyzes 7 dimensions (scope, integration, infrastructure, knowledge, risk, testing, decomposability) to return SIMPLE, STANDARD, or COMPLEX tier with confidence scoring. Includes intent confirmation gating and review agent selection hints for consensus-review integration.
Multi-agent consensus code review with adaptive budgets, complexity-aware agent selection, multiple consensus protocols (Approval/Veto, AAD, CI, Supermajority), cross-agent coverage tracking, context-folding isolation, and progressive summarization. Use when reviewing PRs, directories, or code changes.
Use when executing complex sub-tasks that need context isolation - creates branches with token budgets that auto-cleanup on return
Use when writing Go code, reviewing Go PRs, or asking "is this idiomatic Go?", "how should I structure this in Go?", "what's the Go way to do X?". Provides Effective Go principles for development guidance and code review reference. Covers Go 1.18+ generics, Go 1.22+ iterators, modern testing, and tooling.
Uses power tools
Uses Bash, Write, or Edit tools
Share bugs, ideas, or general feedback.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge.
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Opinionated workflow guides and best practices - the preacher's proven patterns for Claude Code projects
Agent enforcement framework — context injection, planning gates, session learning
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Interactive setup wizard for configuring any repository with Claude Code best practices, based on Boris Cherny's workflow
Harness-native ECC plugin for engineering teams - 64 agents, 262 skills, 84 legacy command shims, reusable hooks, rules, MCP conventions, and operator workflows for Claude Code plus adjacent agent harnesses
v9.44.0 — Patch release for cursor-agent smoke checks in untrusted workspaces. Run /octo:setup.
Terminal Elegance design system compliance checking for FyrsmithLabs products. Audits CSS, templates, and documentation for hardcoded values, accessibility issues, and brand consistency.
Cross-session memory and learning for Claude Code. Provides semantic search, memory recording with category classification, session-level granularity, checkpoints, error remediation, conversation indexing, self-reflection, and multi-agent orchestration via the contextd MCP server (requires contextd v0.4.0+).
A Claude Code plugin marketplace providing skills, commands, and agents for fyrsmithlabs project standards and workflows.
Before installing, ensure you have:
gh) 2.0+ - Required for planning features (install)Add the marketplace to your Claude Code settings:
# Install via Claude Code plugin marketplace
claude plugin install fyrsmithlabs/marketplace
# Initialize a project with standards
/fs-dev:init
# Run a brainstorm session for a new feature
/fs-dev:brainstorm "Add user authentication"
# Check your daily standup
/fs-dev:standup
# Run multi-agent code review
/fs-dev:consensus-review
This marketplace contains three plugins that can be installed independently:
| Plugin | Version | Components | Purpose |
|---|---|---|---|
| fs-dev | 1.9.1 | 13 skills, 15 agents, 12 commands | Development standards, workflows, planning |
| contextd | 1.2.0 | 5 skills, 2 agents, 8 commands | Cross-session memory via MCP |
| fs-design | 1.0.0 | 1 skill, 2 agents, 1 command | Design system compliance |
Set up a project to follow fyrsmithlabs standards with interactive wizard, auto-detection, and compliance checking.
# Full interactive wizard
/fs-dev:init
# Audit compliance without making changes
/fs-dev:init --check
# Quick setup (skip wizard)
/fs-dev:init --quick
# Check for drift from standards
/fs-dev:init --validate
Interactive design interview with complexity assessment, requirements gathering, and GitHub planning.
# Start a brainstorm session
/fs-dev:brainstorm "Add OAuth support"
# Brainstorm creates GitHub Issues automatically in Phase 6
Run parallel code review with 6 specialized agents. All agents have veto power by default. Features adaptive token budgets, context-folding isolation for large scopes, and progressive summarization.
# Review staged changes
/fs-dev:consensus-review
# Review specific path
/fs-dev:consensus-review src/auth/
# Ignore veto power (advisory only)
/fs-dev:consensus-review --ignore-vetos
# Run subset of agents
/fs-dev:consensus-review --agents security,code-quality,go
Save your session state for later resumption. Essential before clearing context or ending a session.
# Save current session state
/contextd:checkpoint
# Checkpoints capture:
# - Accomplishments
# - In-progress work
# - Next steps
Audit CSS, templates, and documentation for Terminal Elegance design system compliance.
# Scan default locations
/fs-design:check
# Check specific file
/fs-design:check static/css/main.css
# Check directory
/fs-design:check internal/templates/
# 1. Design the feature
/fs-dev:brainstorm "Add user authentication"
# 2. Create GitHub issues (automatic from brainstorm Phase 6)
# or manually:
/fs-dev:plan "Add user authentication"
# 3. Code implementation...
# 4. Multi-agent code review
/fs-dev:consensus-review
# 5. Commit with standards
git commit -m "feat: add user authentication"
# 1. Check current state
/contextd:status
# 2. Search for relevant past learnings
/contextd:search authentication patterns
# 3. Work on tasks...
# 4. Save progress before clearing context
/contextd:checkpoint
# 5. Record what you learned
/contextd:remember
# Full codebase analysis
/fs-dev:discover
# Security-focused analysis
/fs-dev:discover --lens security
# Performance-focused analysis
/fs-dev:discover --lens performance
# Today's status with GitHub PR/Issue synthesis
/fs-dev:standup
# Weekly summary
/fs-dev:standup --week