- Home
- Skills
- Agents & Orchestration
- cms site planner
cms site planner
Generates phased implementation plans and developer rule files for Astro, Cloudflare, and Supabase projects.
Free
Works with the AI Agents you already use
cms site planner
Example session with this skill installed
I need to plan a new real estate site. It needs a blog, a photo gallery for listings, and multi-language support. We are using Astro, Cloudflare, and Supabase. I have no brief yet.
- Read your context and instructions
- Compiled the cms site planner
I have initialized the planning phase for your real estate site. Based on your requirements, I have selected the blog, gallery, media, and i18n modules.
Project Documentation
I have generated the five core planning files in your current directory.
Implementation Plan Summary
| Phase | Version | Focus | Rationale |
|---|---|---|---|
| Phase 1 | v0.1.0 | Core Infrastructure | Establish Supabase Auth and RLS boundaries before data entry. |
| Phase 2 | v0.2.0 | Media & Gallery | Setup Cloudflare/Supabase storage for high-res property images. |
| Phase 3 | v0.3.0 | Content & i18n | Implement Astro SSR routing for localized property listings. |
| Phase 4 | v0.4.0 | Public Launch | Finalize public-facing blog and SEO optimizations. |
Generated CLAUDE.md Rules (Snippet)
# Project Rules: Real Estate CMS
## Tech Stack
- Astro (SSR mode) on Cloudflare Workers
- Supabase (Postgres, Auth, Storage)
## Module Specifics: i18n
- All content tables must include a `language_code` column.
- Use Astro middleware for locale detection and routing.
## Module Specifics: Media
- Use Supabase Storage buckets with RLS for property images.
- Images must be served through a transformation proxy for optimization.
Next steps
- Review the
implementation_plan.mdto confirm the phase boundaries meet your timeline. - Check
status.mdfor the list of open items regarding the specific property attributes. - Run the Phase 1 checkpoint to verify your Supabase connection string.
Connects securely to your tools. The creator never sees your data.
About this skill
Planning a new CMS project often results in scattered requirements and vague roadmaps. This skill transforms a website brief into a structured, phased development plan with integrated project rules and tracking documents.
What it does
- Architects implementation plans by breaking the build into versioned phases with specific rationales and checkpoints.
- Generates project rules by creating a tailored
CLAUDE.mdcontaining only the relevant constraints for your specific modules. - Establishes tracking systems through
status.mdandCHANGELOG.mdfiles to monitor phase progress and verification records. - Documents institutional knowledge by initializing a
lessons.mdfile to capture architectural decisions during the build. - Enforces stack consistency by aligning all documentation with Astro SSR, Cloudflare Workers, and Supabase.
How it works
- Analyze input documents to extract existing requirements from your brief or development folders.
- Conduct a gap interview to resolve ambiguities regarding modules like i18n, media, blog, or roles.
- Derive development phases based on the selected feature set and technical risk profile.
- Generate the five core files into your project directory using pre-defined templates.
Frameworks & tools
This skill is optimized for a specific stack: Astro SSR hosted on Cloudflare Workers, using Supabase for Postgres, Auth, and Storage. It assumes the use of Row-Level Security (RLS) and a custom admin dashboard within the same application.
Why this beats prompting it yourself
Writing project scaffolding manually leads to inconsistent rules and missing edge cases for specific Supabase modules. This skill ensures that your CLAUDE.md and phase plan are perfectly synced with the exact modules you chose, preventing technical debt before the first line of code is written.
Use cases
- Start a new client project with ready-to-use status tracking and developer rules.
- Transition a rough website brief into a technical implementation roadmap.
- Set up a standard documentation structure for an Astro and Supabase greenfield build.
- Standardize team workflows by enforcing specific RLS and Cloudflare Worker constraints.
Known limitations
This skill is for greenfield projects only and does not support existing codebases. It generates documentation and planning files but does not write or execute application code.
How to use
Skills on Agensi run inside your AI agent. Copy the prompt, paste it into your agent, and it connects to Agensi and installs this skill for you. If a payment is needed, your agent shows it to you first.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
Free forever
No account required to browse
Trust & safety
Security scanned
Verified clean 11 days ago
- Free to download with an account