This skill resumes, continues, or checks status of a cogni-website project. It is the primary re-entry point for returning to website work across sessions. It should be triggered when the user mentions "continue website", "resume website", "website status", "where was I", "Website fortsetzen", "Website-Status", "weiter mit der Website", "was fehlt noch", "pick up where I left off", "website status check", or opens a session involving an existing website project — even without saying "resume" explicitly.
From cogni-websitenpx claudepluginhub cogni-work/insight-waveThis skill is limited to using the following tools:
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Calculates TAM/SAM/SOM using top-down, bottom-up, and value theory methodologies for market sizing, revenue estimation, and startup validation.
Detect the current state of a website project, show progress, and route to the appropriate next skill.
Scan for website-project.json in:
cogni-website* or *-websiteIf not found, inform the user and suggest website-setup.
Read available files and determine the project phase:
| File Exists | Phase | Status |
|---|---|---|
website-project.json only | Setup complete | Needs plan |
+ website-plan.json | Plan complete | Needs build |
+ output/website/index.html | Build complete | Ready for preview |
+ output/website/css/style.css + pages | Fully built | Ready for deployment |
Count:
Website-Projekt: {slug}
Phase: {current phase}
Unternehmen: {company name}
Theme: {theme name}
Sprache: {language}
Geplante Seiten: {N}
Erstellte Seiten: {M} / {N}
Fehlende Seiten: {list if any}
Letzte Änderung: {date}
Based on the state:
| State | Recommendation |
|---|---|
| Setup complete, no plan | → /website-plan — Seitenstruktur planen |
| Plan complete, no build | → /website-build — Website generieren |
| Build complete | → /website-preview — Website prüfen |
| Build outdated (sources newer than build) | → /website-build — Website aktualisieren (Quellen geändert) |
| Partially built (some pages missing) | → /website-build — Fehlende Seiten generieren |
If the site is already built, check if source content has changed since the last build:
website-plan.json source_files) vs. output HTML filesRe-run content discovery using the same globs as website-setup and compare against the content_discovery counts stored in website-project.json:
**/tips-project.json and **/output/report.md that were not present when the project was created (i.e., sources.trends_project or sources.research_projects is null/empty but projects now exist) → suggest re-running setup to discover new content sourcesPresent changes:
Änderungen seit letztem Build:
Neue Inhalte:
✚ 2 neue Marketing-Artikel
✚ 1 neues Produkt im Portfolio
Neue Inhaltsquellen verfügbar:
✚ Trend-Report gefunden (vorher nicht eingebunden)
Empfehlung: /website-setup erneut ausführen, um neue Quellen einzubinden
Add to recommendation table:
| State | Recommendation |
|---|---|
| New content sources discovered | → /website-setup — Neue Quellen einbinden, dann erneut planen |
| New entities in existing sources | → /website-plan — Seitenstruktur aktualisieren |