skills.rest
joelklabo
joelklaboCOMMUNITY
Explore all skills by this author →
Website𝕏@joelklaboGitHub

nostrstack-dev-workflow

Run deterministic local development and debugging workflows for the nostrstack repository.

Updated Dec 31, 2025
Search Tags:#troubleshooting#logs#mcp#chrome-devtools#dev-workflow#regtest#nostrstack
One-click install
npx skills add https://github.com/joelklabo/markdowntown-cli --skill nostrstack-dev-workflow
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: nostrstack-dev-workflow
Source: https://github.com/joelklabo/markdowntown-cli/tree/main/codex/skills/nostrstack-dev-workflow
Command: npx skills add https://github.com/joelklabo/markdowntown-cli --skill nostrstack-dev-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a clear, repeatable local development and debugging workflow for the nostrstack repository so engineers can reproduce issues, keep required logs visible, and validate UI, network, and payment behaviors reliably.

Core Features & Use Cases

  • Keep API and gallery logs visible while reproducing and fixing bugs to capture deterministic evidence.
  • Verify UI changes in Chrome DevTools via the MCP bridge and use a Playwright QA fallback when MCP is unavailable.
  • Run regtest stacks for local payments and demo flows, and consult targeted troubleshooting and testing matrices for environment setup.
  • Use case: a developer reproduces a payment-related UI bug by starting the regtest stack, tailing API/gallery logs, validating network/console state in MCP, and running Playwright QA if MCP fails.

Quick Start

Start development with make dev, tail the API and gallery logs, verify the UI via the MCP Chrome bridge, and use the Playwright QA fallback if MCP is unavailable.

Frequently Asked Questions about nostrstack-dev-workflow

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reproduce and debug nostrstack locally?▼

To reproduce and debug nostrstack locally, run make dev, tail the live API and gallery logs, validate UI behavior in Chrome DevTools via the MCP bridge, and use Playwright QA as a fallback for verification.

What is the best way to keep nostrstack logs visible while fixing bugs?▼

The best way to keep logs visible during nostrstack development is to maintain live API and gallery log tails simultaneously while reproducing issues, ensuring you capture deterministic evidence of bugs and network behavior.

Can I verify nostrstack UI changes if the MCP Chrome bridge is unavailable?▼

Yes, you can verify nostrstack UI changes using the Playwright QA fallback when the MCP Chrome DevTools bridge is unavailable, ensuring consistent UI testing and network state validation.

How do I test local payments in the nostrstack development workflow?▼

You test local payments in the nostrstack workflow by running regtest payment stacks, tailing API and gallery logs, and validating network and console state through the MCP Chrome DevTools bridge.

Why are my nostrstack regtest services not working during local development?▼

If nostrstack regtest services are not working, consult the referenced troubleshooting and testing matrices to validate environment setup, ensure make dev started correctly, and verify live API and gallery logs.

Related Skills

Explore More Software Engineering Skills→
joelklabojoelklabo

nostrstack-embed-ui

Apply design tokens and CSS classes to @nostrstack/embed components.

Community
Intermediate
joelklabojoelklabo

nostrstack-lightning

Integrate LNbits payment flows into nostrstack with regtest and smoke tests.

Community
Intermediate
jmaglyjmagly
175

gate-evaluation

Validate phase-gate criteria and generate pass/fail gate reports.

Community
Advanced
NaveedTechLabNaveedTechLab
11

browser-payment-mcp

Automate payment portal interactions with Playwright and human approval.

Community
Advanced