Frontend Planning Html

職業

カテゴリ

技術ドキュメント

• index.html
• style.css
• app.js

10. Include all sitemap pages as individual .html files in each pass folder.
11. Ensure every page is cross-linked and fully navigable without authentication.
12. Update .docs/planning/frontend/comparison.md with style notes and review prompts.

Guardrails

• Do not use frameworks for ideation concepts.
• Keep concepts self-contained and easy to open locally.
• Prioritize visual differentiation between styles.
• Include responsive behavior for mobile and desktop.
• Include lightweight interactivity in app.js only when it supports concept review.

Output Expectations

• Five style concepts by default unless the user explicitly requests a different count or style set.
• Support multiple passes; default one pass unless user requests more.
• Each pass must represent a full frontend prototype for all sitemap pages and key feature flows.
• A concise comparison sheet describing strengths/tradeoffs for each concept.
• Clear mapping between style name, pass number, and concept folder path.

References

• Read .codex/skills/frontend-planning-html/references/default-styles.md when selecting or extending style directions.