Main development command for Astro/Starlight projects - implements features, fixes bugs, creates components
/plugin marketplace add superbenefit/sb-marketplace/plugin install astro-dev@sb-marketplaceThe primary development command for Astro and Starlight projects. Handles everything from simple components to complex features with intelligent validation.
/dev [description of what to build]
/dev [description] --audit=off # Skip validation
/dev [description] --audit=light # Quick validation (5 checks)
/dev [description] --audit=comprehensive # Full validation (50+ checks)
The /dev command loads the astro-coding skill (best practices, patterns, critical rules) and implements your request. It automatically validates code based on task complexity, or you can control validation with the --audit flag.
/dev Add a Footer component with social links and copyright
Result: Footer.astro with proper TypeScript types, accessibility, and styling
/dev Add a blog with categories and pagination
Result: Content collection, dynamic routes, category pages, pagination component
/dev Fix all TypeScript errors in the components folder
Result: All type errors resolved following Astro best practices
/dev Create a multi-language content system with external data integration
Result: Custom loaders, i18n routing, data transformation, full implementation
/dev Add Tailwind CSS integration to the project
Result: Updated astro.config with Tailwind, installed packages, example styles
By default, /dev validates your code automatically:
| Task Size | Files Changed | Default Validation |
|---|---|---|
| Small | 1 file, <20 lines | Light (5 critical checks) |
| Medium | 2-5 files, <100 lines | Medium (20 checks) |
| Large | >5 files or >100 lines | Comprehensive (50+ checks) |
| Security | Auth, payments, secrets | Always comprehensive |
# Skip validation for quick experiments
/dev Add a test component --audit=off
# Force full validation for critical code
/dev Update API endpoint --audit=comprehensive
# Light validation for simple changes
/dev Fix typo in header --audit=light
The astro-coding skill loads patterns based on your request:
Always loaded (~100 tokens):
Context-loaded (~400 tokens):
On-demand (~800 tokens):
Every implementation follows these rules:
import './Header.astro' not import './Header''astro:content' not 'astro/content'class not className in .astro files❌ /dev make a blog
✅ /dev Create a blog collection with title, date, author, tags, and draft status
✅ /dev Add authentication (using existing Supabase setup)
✅ /dev Create footer (must match existing header style)
✅ /dev Add blog with categories, tags, RSS feed, and author pages
All parts will be implemented together efficiently.
✅ /dev Add pagination to blog (like the docs pagination)
✅ /dev Create Card component (similar to existing Button style)
/lookup [query] → Quick API reference lookup
/lookup getCollection
/lookup client directives
/lookup getStaticPaths
/design [system] → Architecture planning for complex systems
/design multi-tenant content system with GitBook integration
## Implementation Complete
### Files Created/Modified
- src/components/Footer.astro (created)
- src/pages/blog/[slug].astro (modified)
- src/content/config.ts (modified)
### Changes Made
[Clear description of what was implemented]
### Validation Results
✅ All imports have extensions
✅ TypeScript types defined correctly
✅ No security issues
✅ Performance optimized
✅ Accessibility considered
**Validation Level**: Medium (20 checks passed)
### Usage Example
\`\`\`astro
import Footer from '../components/Footer.astro';
<Footer />
\`\`\`
Ready to use! Test by running `npm run dev`
/dev Create a Card component with title, description, image, and link props
/dev Add dynamic route for blog posts with proper TypeScript types
/dev Set up a docs collection with frontmatter validation
/dev Create API endpoint at /api/posts that returns published blog posts
/dev Add React integration and configure for client components
/dev Refactor Header component to use Astro props instead of slots
Check that file extensions are included: ./Component.astro not ./Component
Make sure Props interfaces are defined for all components
Verify client directives: client:load, client:visible, client:idle
Ensure src/content/config.ts exports collections and schema is valid
Command Version: 2.0 (v0.4.0)
Replaces: /develop and /implement from v0.3.x
Compatible with: astro-dev plugin v0.4.0+
Last Updated: 2025-11-05
Use /dev for all your Astro/Starlight development needs - from quick components to complex features.
/devExtreme lightweight end-to-end development workflow with requirements clarification, intelligent backend selection, parallel codeagent execution, and mandatory 90% test coverage
/devExtreme lightweight end-to-end development workflow with requirements clarification, parallel codeagent execution, and mandatory 90% test coverage