Installs into .claude/skills of the current project.
Are you the author of Docs Portal?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/yasik-docs-portal)
---
name: docs-portal
description: Rebuild and verify the AgentLane website documentation portal after docs-sync or edits to root documentation, navigation, or portal rendering.
---
# Documentation portal
Keep public Markdown in root `docs/`. Astro reads those files directly.
`docs/plans/` is internal and must stay out of routes, navigation, and search.
## Workflow
1. If you change documentation prose, use `dev-docs` from the session's skill
catalog. Apply its review checklist to the changed pages. Reuse a completed
review from docs-sync when the text has not changed. If the skill is missing,
report that limitation and do not claim a completed style review.
2. Use Node.js 24 and pnpm 10.29.3. From the repository root, install the website
dependencies with `make -C website install` if needed.
3. Run `make -C website check`. This checks formatting and types, builds the
website from root documentation, and tests the generated routes and links.
4. Fix failures within the changed scope and repeat the check. For layout or
interaction changes, use `make -C website dev` to check a changed page on
desktop and mobile. Check navigation, search, code blocks, and both themes.
5. Report the source pages, check results, and unresolved failures. Generated
files stay in ignored `website/dist/`; do not commit them.
The build creates `/docs/` from `docs/README.md`. Other Markdown files retain
their relative path without `.md`; nested README files use directory routes.
The build derives navigation and search from the same public collection.
Use relative Markdown links in source files so they also work on GitHub.
The website workflow runs on public docs changes. Deployment uses the website's
normal release process. A local rebuild does not publish the site.
