feat(landing): add landing package to monorepo#7
Merged
Conversation
Next.js 16 + React 19 + Tailwind 4 static landing template with token-driven theming via src/content/site.ts. Canonical 8-route structure (/, /mobile, /business, /pricing, /blog, /contact, /privacy, /terms) shared across ventures — only content varies. Moved from reineira-atlas/.claude/templates/landing/ to keep application code in platform-modules, alongside backend and app. The scaffold pipeline in atlas now ships landing via the existing rsync of platform-modules into each venture.
0xkkkn
added a commit
to ReineiraOS/reineira-atlas
that referenced
this pull request
Apr 24, 2026
The landing template is application code, not agent instructions — it belongs in platform-modules alongside backend/app, not in atlas. Atlas holds only the populate-landing skill (content logic) and claude-design skill (token polish). The template files themselves ship through the existing platform-modules rsync in bootstrap Step 1. Changes: - Delete .claude/templates/landing/ (moved to platform-modules PR) - Rename scaffold-landing skill to populate-landing (no more rsync step) - bootstrap.md Step 1: include packages/landing/package.json in rebrand - bootstrap.md Step 1b: replace rsync with /populate-landing call - Update refs in _builder.md, claude-design, brief.template.md Paired with ReineiraOS/platform-modules#7
Merged
5 tasks
CI format:check failed because landing files were authored without running prettier. Applied pnpm format locally. No semantic changes.
- .prettierignore: skip CHANGELOG.md (semantic-release-generated) and **/next-env.d.ts (next-generated) to unblock format:check - ci.yml: add "Lint landing" step mirroring backend/app lint steps
|
🎉 This PR is included in version 0.3.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
packages/landing/— a Next.js 16 + React 19 + Tailwind 4 static landing template — as the third application starter alongsidebackendandapp.The template is canonical: same 8-route structure, same component sequence, same animations across every venture. Only text, images, and design tokens vary per venture (driven by
src/content/site.ts+src/content/design.ts).Routes
/— home/mobile— mobile product page/business— business product page/pricing— pricing/blog+/blog/[slug]— blog/contact— contact / departments/privacy,/terms— legalContext
Previously this template lived inside
reineira-atlas/.claude/templates/landing/(PR #7 in atlas). That placed application code in the Startup OS repo, which should only hold agents, skills, and docs. Moving the template here keeps the separation clean:Atlas's
/bootstrappipeline already doesrsync -a ../platform-modules/ ../<venture>/, so the landing package ships to every venture through the existing scaffold step — no new copy step needed. The companion atlas PR #7 will be updated to drop the inline template and rename the skill fromscaffold-landingtopopulate-landing(fillssite.tsfrom brief).Test plan
pnpm installat root resolves with workspace config unchangedpnpm -F @reineira-os/modules-landing typecheck→ 0pnpm -F @reineira-os/modules-landing build→ 0, 13 static pages prerenderedpnpm -F @reineira-os/modules-landing lint→ 0pnpm -F @reineira-os/modules-landing dev+ curl all 8 routes → 200