How the @nuclia/core SDK is structured and how to use it correctly in this monorepo. Covers SDK architecture (Nuclia class, rest/db/auth layers, KnowledgeBox, RetrievalAgent), adding new API calls, wrapping SDK calls in Angular services in @flaps/core, error handling patterns, and URL routing (global vs regional backends). Activate this skill whenever a task involves calling the Nuclia API, adding a new endpoint, extending KnowledgeBox or RetrievalAgent, creating an Angular service that fetches data, working with SDKService, or handling HTTP errors. Do not wait for the user to say "SDK" — if they ask for "a service that fetches X from the API" or "add support for endpoint Y", this skill applies.
Domain knowledge about the Nuclia / Progress Agentic RAG platform. Use this skill when discussing product features, platform capabilities, API behaviour, UX decisions, or how the platform works end-to-end. Also use when planning a new feature to validate it against the platform's existing capabilities and constraints before building.
Angular 21 patterns as used in the Nuclia frontend monorepo — covering OnPush change detection, inject() dependency injection, NgModule-based components (default), signal-based state, RxJS↔Signal bridges, functional guards, and lazy routing. Activate this skill for ANY Angular task in this repo: creating or modifying components, writing services, managing state, adding routes or guards, refactoring legacy code to modern patterns, debugging change detection issues, or deciding which state management tier to use. Do not wait to be asked about "Angular patterns" specifically — if the task involves TypeScript files in apps/ or Angular libs/, this skill applies. Also use when migrating from @Input/@Output decorators or constructor injection to the modern Angular 21 style.
Keeps all AI-agent documentation in sync with the codebase: root AGENTS.md, per-project AGENTS.md files in apps/ and libs/, and knowledge embedded in .github/skills/ and .github/agents/. Activate this skill when the user mentions syncing docs after a PR or commit, asks "what docs need updating?", says "update knowledge", references a big feature that just landed ("there was a big update in commit X"), or runs the staleness check script and sees stale files. Also activate proactively when you notice an AGENTS.md file is missing for a project that was just created, or when a skill references a pattern that no longer matches the source code. Do NOT wait for the user to explicitly say "knowledge sync" — if code has changed and docs might be stale, this skill applies immediately.
Reviews and refactors AGENTS.md files in the Nuclia frontend monorepo for completeness, accuracy, and AI-agent usability. Invoke this skill whenever you are working with an AGENTS.md file in apps/ or libs/, when asked to review or improve agent documentation, when creating a new AGENTS.md for a project, or when you notice that an AGENTS.md seems outdated, thin, or missing. Proactively suggest a review even when the user only asks an unrelated question about a project if no AGENTS.md exists for it.
Deeply scans code for runtime bugs, logic errors, and correctness defects in the Nuclia frontend monorepo. Use this skill whenever code needs to be audited for actual bugs rather than style issues — including during code review, when a user reports unexpected behaviour, when writing or reviewing a PR, or when asked to "find bugs", "check for bugs", "is this correct?", or "what could go wrong here?". This skill is intentionally narrow: it reports only things that are broken or will likely break at runtime, not style, architecture, or best-practice nudges (those belong in code-review). Designed to be invoked by automated agents as well as interactively.
Performs a focused code review of changed files or PR diffs in the Nuclia frontend monorepo. Activates when the user explicitly says "review", "code review", "review this PR", "review this diff", "review these changes", or "review this file". Checks changed code against all repo standards: Angular 21 patterns, RxJS best practices, design system usage, SDK patterns, module boundaries, test coverage, and general TypeScript hygiene. Returns a flat list of findings grouped by file with a severity label for each.
Expert knowledge of the Nuclia design system — @nuclia/sistema and @guillotinaweb/pastanaga-angular. Use this skill whenever a task involves ANY of the following: creating or modifying Angular UI components in dashboard, rao, manager-v2, or nucliadb-admin; using or overriding design tokens (colours, spacing, typography); adding icons, modals, toasts, dropdowns, tables, tabs, form fields, or any pa-/nsi- prefixed component; styling with SCSS tokens or utility classes; implementing settings pages, configuration rows, cards, badges, labels, progress indicators, or navigation elements. Don't wait to be asked explicitly about design system — if the task is about frontend UI in this monorepo, this skill applies.