Complete project memory and specification management for Claude Code
This plugin is not yet in any themed marketplace. To install it, you'll need to add it from GitHub directly.
This plugin uses advanced features that require additional trust:
Only install plugins from repositories you trust. Review the source code before installation.
Choose your preferred installation method below
A marketplace is a collection of plugins. Every plugin gets an auto-generated marketplace JSON for individual installation, plus inclusion in category and themed collections. Add a marketplace once (step 1), then install any plugin from it (step 2).
One-time setup for access to all plugins
When to use: If you plan to install multiple plugins now or later
Step 1: Add the marketplace (one-time)
/plugin marketplace add https://claudepluginhub.com/marketplaces/all.jsonRun this once to access all plugins
Step 2: Install this plugin
/plugin install project-continuity@allUse this plugin's auto-generated marketplace JSON for individual installation
When to use: If you only want to try this specific plugin
Step 1: Add this plugin's marketplace
/plugin marketplace add https://claudepluginhub.com/marketplaces/plugins/project-continuity.jsonStep 2: Install the plugin
/plugin install project-continuity@project-continuityA comprehensive Claude Code plugin for maintaining development continuity, specifications tracking, and memory management across coding sessions.
👉 First time? Read the Team Guide for a complete tutorial with real-world examples!
claude plugin install github:BlackfishSpirit/claude-project-continuity-plugin
git clone https://github.com/BlackfishSpirit/claude-project-continuity-plugin.git
cd claude-project-continuity-plugin
claude plugin marketplace add .
New to the plugin? Check out the Team Guide for:
/init-project my-awesome-app
This command will:
.claude directory structureCLAUDE.md with project contextdocs/ folder with specifications and progress trackingProject Setup:
/init-project [name] - Initialize project with continuity systemDevelopment:
/validate-spec - Validate implementation against specifications/update-progress - Update progress trackingDesign Workflow:
/design-start - Initialize design project/design-layout - Generate layout iterations/design-theme - Create theme variations/design-implement - Add interactivity and animations/design-agent - Comprehensive design guidance/design-review - Quality assurance checkSession Management:
/session-start <type> - Start focused development session (frontend, backend, auth, payments, testing, devops, project-management, fullstack)/session-end <id> - End session and save context/session-info - Learn about session managementLinear Integration:
/linear-init <name> <type> - Initialize Linear project with complete label structure (greenfield/brownfield)/sync-linear pull - Load Linear issues into memory for session tracking/sync-linear push - Update Linear issues with session work and commentsMaintenance:
/compact-memory - Compact and optimize memory storage/sync-team - Sync decisions with team repositoryarchitect - Technical design and architecture decisionsimplementer - Code implementation following specificationsreviewer - Code review and quality assurancedocumenter - Documentation generation and updatesdesign-workflow - Complete UI/UX design process with SuperDesign integrationProblem: With multiple MCPs (Tailwind, Supabase, Stripe, Playwright, etc.), you can consume 40k+ tokens before writing any code, leaving limited context for actual work.
Solution: Session-based MCP management lets you load only the tools you need for your current work:
# Frontend session (~8k tokens instead of 40k)
mcpick # Select .mcp-frontend.json
claude
> /session-start frontend
# Backend session (~12k tokens)
mcpick # Select .mcp-backend.json
claude
> /session-start backend
Key Benefits:
Available Session Types:
design - UI/UX design and prototyping (SuperDesign, Tailwind, shadcn/ui, Firecrawl)frontend - UI development (Tailwind, shadcn/ui)backend - API/database work (Supabase, Postgres, Prisma)auth - Authentication (Clerk, Supabase Auth)payments - Payment processing (Stripe)testing - E2E testing (Playwright)devops - CI/CD and deployment (GitHub, Docker, Coolify)project-management - Task tracking (Linear)fullstack - All tools loaded (use sparingly)Setup:
cp -r [plugin-dir]/templates/mcp-configs/.mcp-*.json ~/myproject/npm install -g mcpickmcpick → Select config → claude → /session-start <type>See Session Management Guide for detailed workflows and examples.
Complete Linear.app integration for seamless issue tracking across development sessions.
Set up Linear credentials:
# .env
LINEAR_API_KEY=lin_api_xxxxxxxxxxxxx
LINEAR_TEAM_ID=your-team-id
Initialize Linear project:
claude
> /linear-init "My SaaS App" greenfield
Sync issues to session:
> /session-start project-management
> /sync-linear pull
# Morning: Pull issues
> /session-start project-management
> /sync-linear pull
# → Loads 15 active issues into memory
# Work on frontend
> /session-start frontend
> @project-memory link_issue_to_session
session_id: 43
linear_issue_number: "DEV-123"
work_description: "Building dashboard UI"
# → Work on the issue...
# End session
> /session-end 43
# Sync back to Linear
> /sync-linear push
# → Updates DEV-123 with session summary and changes status
Linear.app (Source of Truth)
↓ pull
Memory Database (Cache + Session Links)
↓ link
Development Sessions (Focused Work)
↓ push
Linear.app (Updated with Progress)
Session-Issue Management:
link_issue_to_session - Connect Linear issue to current sessionget_session_issues - View all issues for a sessioncache_linear_issue - Store issue locallyget_cached_issues - Query cached issuesSee Linear integration files in lib/ for full API reference.
Complete front-end design workflow with AI-assisted prototyping, theme generation, and component library integration.
Design Workflow:
/design-start - Initialize design project with requirements gathering/design-layout - Generate 3-5 layout iterations with ASCII visualization/design-theme - Create 5 theme variations (modern, glass morphism, professional, etc.)/design-implement - Add interactivity, animations, and functional elements/design-agent - Comprehensive design guidance through all phases/design-review - Quality assurance and accessibility validationInstall SuperDesign VS Code extension
Set up design session:
# Copy design MCP config
cp [plugin-dir]/templates/mcp-configs/.mcp-design.json ~/myproject/
# Start design session
mcpick # Select .mcp-design.json
claude
> /session-start design
Begin 4-phase workflow:
# Phase 1: Layout
> /design-layout "Dashboard with navigation, metrics, and data tables"
# Phase 2: Theme (after generating palette at colors.co)
> /design-theme "Apply modern theme with professional color palette"
# Phase 3: Interactivity
> /design-implement "Add hover effects, transitions, and animations"
# Phase 4: Convert to production components
@shadcn-ui add-component
component: "card"
# Morning - Design Phase
mcpick # Select .mcp-design.json
claude
> /session-start design
Session ID: 50
> /design-layout "Product page with gallery, specs, pricing"
# Review options, select layout
> /design-theme "Modern theme with blue palette for trust"
# Review variations, select preferred
> /design-implement "Add zoom, tabs, cart animation"
# Test in SuperDesign canvas
> /session-end 50
Summary: "Complete product page design with modern theme"
# Afternoon - Implementation
mcpick # Select .mcp-frontend.json
claude
> /session-start frontend
Session ID: 51
# Convert design to shadcn components
@shadcn-ui add-component
component: "carousel"
# Implement with React/Next.js
> /session-end 51
Summary: "Implemented product page with shadcn components"
Purpose: Visual annotation of existing UIs for design feedback.
Location: .superdesign/tools/dom-annotator.html
Workflow:
Use cases:
Essential Tools:
Documentation:
docs/design-resources.md - Complete design tool guide (50+ resources)docs/design-agent-integration.md - Agent integration details.superdesign/tools/README.md - DOM Annotator technical documentation.superdesign/tools/QUICKSTART.md - 5-minute quick start guideDesign Phase (SuperDesign Canvas)
↓
Theme Application (colors.co, TweakCN)
↓
Interactive Prototype (Animations, Interactions)
↓
Production Conversion (shadcn/ui Components)
↓
Frontend Implementation (React/Next.js)
All design decisions stored in memory for cross-session continuity and team reference.
your-project/
├── .claude/
│ ├── CLAUDE.md # Main project memory
│ ├── memory.db # SQLite decision storage
│ ├── agents/ # Subagent configurations
│ ├── commands/ # Custom commands
│ └── settings.json # Hooks configuration
├── docs/
│ ├── specifications.md # Project specifications
│ ├── progress.md # Task tracking
│ ├── architecture.md # Technical decisions
│ └── decisions/ # Architecture Decision Records
The main memory file is automatically loaded and includes:
Pre and post-write hooks ensure:
git checkout -b feature/amazing-feature)git commit -m 'Add amazing feature')git push origin feature/amazing-feature)MIT License - see LICENSE file for details
Mike Gifford - @BlackfishSpirit
1.0.0