chore(workflow): add AI-assisted workflow commands and configurations

Add comprehensive workflow commands for AI-assisted development:
- Claude commands: analyze, clarify, plan
- Kilocode workflows: full feature development lifecycle
- Opencode commands: specification and implementation workflows
- Roo MCP configuration for tool integration

Update .gitignore to exclude .astro build cache directories.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

specs/001-users-pukpuk-dev/spec.md

@@ -7,6 +7,15 @@
 
 ---
 
+## Clarifications
+
+### Session 2025-10-06
+- Q: What is the expected number of blog posts and portfolio items to be migrated? → A: 35
+- Q: What are the possible states for blog posts? → A: published, draft, schedule publish
+- Q: How will the system handle concurrent edits to the same content item? → A: Last write wins
+- Q: What are the specific security measures for user authentication and data protection? → A: SSL/TLS certificates, input validation, regular security audits
+- Q: What is the expected daily traffic volume for the website? → A: 500-2000 visitors per day
+
 ## User Scenarios & Testing *(mandatory)*
 
 ### Primary User Story
@@ -26,6 +35,7 @@ As a public visitor, I want to browse a fast, well-structured, and informative w
 - What happens when a logged-in user's session expires? (System should redirect to the login page on the next action).
 - How does the system handle a user trying to access an admin URL they don't have the role for? (System should show a "Permission Denied" or 403 error page).
 - What happens if the Payload CMS API is unavailable during the static site build? (The build process should fail with a clear error message).
+- Concurrent edits to the same content item are resolved by "last write wins" (latest save overwrites previous changes).
 
 ---
 
@@ -42,13 +52,19 @@ As a public visitor, I want to browse a fast, well-structured, and informative w
 - **FR-008**: The system MUST provide a functional contact form on the `/contact` page.
 - **FR-009**: The system MUST generate a `sitemap.xml` file based on the content stored in the CMS.
 - **FR-010**: All content types in the CMS MUST include dedicated fields for SEO metadata (meta title, meta description).
+- **FR-011**: The system MUST implement security measures including SSL/TLS certificates, input validation, and regular security audits for authentication and data protection.
 
 ### Key Entities *(include if feature involves data)*
 - **User**: Represents an authenticated user of the admin panel. Attributes: email, password hash, role (`admin` or `editor`).
-- **Blog Post**: Represents a single article. Attributes: title, slug, content, author, category, publication date, SEO metadata.
+- **Blog Post**: Represents a single article. Attributes: title, slug, content, author, category, publication date, state (draft, published, scheduled), SEO metadata. Lifecycle: Can transition from draft to scheduled to published.
 - **Portfolio Item**: Represents a single project. Attributes: title, slug, description, project images, completion date, SEO metadata.
 - **Category**: Represents a blog post category. Attributes: name, slug.
 
+Expected data volume: Approximately 35 blog posts and portfolio items combined.
+
+### Non-Functional Requirements
+- Scalability: Expected daily traffic of 500-2000 visitors.
+
 ---
 
 ## Review & Acceptance Checklist
@@ -61,7 +77,7 @@ As a public visitor, I want to browse a fast, well-structured, and informative w
 - [X] All mandatory sections completed
 
 ### Requirement Completeness
-- [ ] No [NEEDS CLARIFICATION] markers remain
+- [X] No [NEEDS CLARIFICATION] markers remain
 - [X] Requirements are testable and unambiguous
 - [X] Success criteria are measurable
 - [X] Scope is clearly bounded