Activity
Mon
Wed
Fri
Sun
Feb
Mar
Apr
May
Jun
Jul
Aug
Sep
Oct
Nov
Dec
Jan
What is this?
Less
More

Memberships

GET SHIT DONE

54 members • Free

Agentic Labs

487 members • $7/m

2 contributions to GET SHIT DONE
Best practices for integrating Design System with GSD from scratch
Hello everyone, I'm wondering if there's a recommended approach or best practice for setting up a project from the ground up with a consistent design system that integrates well with GSD?
0 likes • 10h
This is more just general "working with AI" advice but I always like to add a phrase about using MCP servers. For example, if I am specifying the tech stack, say "Use Laravel Boost MCP Server" (if using Laravel) and I make sure it is loaded into Claude (claude mcp list) for this project. If you are vibe'n say something like "Use MCP servers for the tech stack if available and either install them or confirm I have installed them before starting coding". If you aren't familiar with MCP servers, they are basically a way for AI to get local project information without scanning files. It is kind of like a cheat sheet and an API to help AI deal with MySQL, Github, n8n, Docker, etc. Speeds things up and uses less token. GSD itself prefers to use "Context7" MCP server if available so that is a good one to add just for GSD.
GSD Workflow Cheat Sheet
GSD Newbie here and kept getting lost in "what command when" so here is a little cheat sheet that shows the common commands used in the various parts of the GSD work loop: Starting a New Project /gsd:new-project → Answer questions, get PROJECT & ROADMAP MDs /gsd:quick → Build a quick feature without full gsd process (v 1.8) Daily Work Loop (within a milestone) /gsd:progress → "Where am I? What's next?" /gsd:discuss-phase N → Capture decisions before planning (don't skip!) /gsd:plan-phase N → Create executable plans /gsd:execute-phase N → Build it /gsd:verify-work N → Test it with Claude's guidance Stopping & Starting /gsd:pause-work → Creates handoff file when stopping mid-phase /gsd:resume-work → Restores context when coming back /gsd:progress → Alternative to resume - shows status & routes you Capturing Ideas While Working /gsd:add-todo → Quick capture without breaking flow /gsd:check-todos → Review captured items Milestone Transitions /gsd:audit-milestone → "Did we actually deliver what we promised?" /gsd:plan-milestone-gaps → Creates phases for anything missing /gsd:complete-milestone → Archives, git tags, prepares for next /gsd:new-milestone → Starts new milestone with full context Adjusting Scope Mid-Flight /gsd:add-phase → Append to end of roadmap /gsd:insert-phase 2.1 → Squeeze in urgent work between phases /gsd:remove-phase N → Remove a future phase
1-2 of 2
Leonard Gallion
2
13points to level up
@leonard-gallion-1491
Software developer

Active 1h ago
Joined Jan 18, 2026
Powered by