nostrstack-dev-workflow
Local development workflow for nostrstack, including running API/gallery with logs, regtest stack usage, MCP Chrome DevTools verification, QA fallback, and environment/setup troubleshooting. Use when starting dev, debugging, reproducing issues, or validating UI/console/network behavior in the nostrstack repo.
When & Why to Use This Skill
The nostrstack-dev-workflow skill is a comprehensive local development assistant designed for the nostrstack repository. It streamlines the developer experience by providing structured workflows for running API and gallery services, monitoring real-time logs, and utilizing advanced debugging tools like MCP Chrome DevTools. By integrating environment setup, issue reproduction, and QA fallback procedures, it ensures a consistent and efficient development cycle for contributors.
Use Cases
- Local Environment Initialization: Quickly set up and start the nostrstack development stack, including API and gallery services with properly configured log tailing.
- UI and Network Debugging: Use the MCP Chrome DevTools bridge to inspect frontend behavior, console outputs, and network requests directly within the development workflow.
- Automated QA and Regression Testing: Execute Playwright-based QA fallbacks to validate UI changes when manual MCP verification is unavailable, ensuring code stability.
- Issue Reproduction and Troubleshooting: Systematically reproduce reported bugs by leveraging the regtest stack and monitoring specific log files for backend and frontend errors.
- Environment Maintenance: Resolve configuration issues and setup bottlenecks using built-in troubleshooting guides for MCP and local demo flows.
| name | nostrstack-dev-workflow |
|---|---|
| description | Local development workflow for nostrstack, including running API/gallery with logs, regtest stack usage, MCP Chrome DevTools verification, QA fallback, and environment/setup troubleshooting. Use when starting dev, debugging, reproducing issues, or validating UI/console/network behavior in the nostrstack repo. |
Nostrstack Dev Workflow
Follow this workflow when working in the nostrstack repo.
Core workflow
- Read
references/dev-workflow.mdfor the required log + UI verification steps. - Keep API + gallery logs visible while reproducing and fixing.
- For UI changes, verify in Chrome DevTools MCP; if MCP is unavailable, run the Playwright QA fallback.
Commands checklist
- Start logs:
pnpm dev:logs(ormake dev) and tail.logs/dev/api.log+.logs/dev/gallery.log. - MCP Chrome bridge:
./scripts/mcp-devtools-server.sh+./scripts/mcp-chrome.sh. - QA fallback:
pnpm qa:regtest-demo.
When to read more
- Troubleshooting MCP:
references/mcp-setup.md. - Local demo/regtest flows:
references/local-demo.md. - Testing matrix and env:
references/testing.md.