Create and host standalone public landing pages under the operator app.
npx skills add https://github.com/cogni-dao/cogni --skill landing-page-cogni-dao
Please help me install this Agent Skill. Skill: landing-page Source: https://github.com/cogni-dao/cogni/tree/main/.claude/skills/landing-page Command: npx skills add https://github.com/cogni-dao/cogni --skill landing-page-cogni-dao
Build public landing pages as standalone operator-hosted pages, not as replacements for the main homepage. It preserves / as the canonical operator homepage unless explicitly told otherwise, creates standalone public routes such as /internship, reuses the local UI kit and theme tokens, and adds a public form/API only when the page needs intake.
Create a new public route under nodes/operator/app/src/app/(public)/<slug>/page.tsx and build the page using the existing UI kit and theme tokens.
High-intent search queries and answers about installing and using this skill.
To build a standalone public landing page in Next.js without replacing your main homepage, create a new public route under a (public) directory. This enforces a route contract that preserves the canonical / path intact while hosting the new page at a custom slug.
Yes, you can reuse your existing UI kit and theme tokens for a custom operator campaign page. The system is designed to ensure visual consistency by leveraging the local operator UI kit rather than requiring an external component library.
To add a public intake form to an operator-hosted internship or demo page, you can include a lightweight public form or API. This allows the page to capture minimal, non-sensitive user input only when the specific campaign requires it.
The best way to organize public routes for founder profiles in a Next.js app is using standalone operator-hosted pages. You create individual public routes like /founder-name under a dedicated (public) folder, keeping them separate from internal application logic.
No, adding a public route does not affect the canonical homepage routing contract. The system explicitly preserves the / path as the main operator homepage unless explicitly told otherwise, maintaining the structural integrity of your Next.js routing.
You should not use standalone operator landing pages when your public content requires capturing sensitive user data. The intake forms are designed to capture only minimal, non-sensitive data, making this approach unsuitable for secure or private data collection workflows.
PolicyEngineEnforce Tailwind CSS v4, ui-kit, and Next.js App Router frontend specifications.
MikeyMiamiStandardize web form data capture and automation enrollment logic.
serguei9090Guides React component development with @lobehub/ui, antd-style, and hybrid routing conventions.
mahg-esGenerate static websites from Markdown into deployable HTML with CI workflows.
