Error Handling â Nuclia Frontend Monorepo
openbooklet.com/s/error-handling-nuclia-frontend-monorepoopenbooklet.com/s/error-handling-nuclia-frontend-monorepo@1.0.0GET /api/v1/skills/error-handling-nuclia-frontend-monorepoErrors in this codebase come from two different SDK contracts depending on which method is called. Getting these mixed up is the most common error-handling mistake.
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.
This skill encodes patterns as they are **actually used** in this codebase. Angular 21 has many features; this covers only what the team has adopted. When in doubt, match existing code.
This skill describes how `@nuclia/core` (the JS/TS SDK) is structured and how Angular services in `@flaps/core` wrap it. Before adding any new API call, read this to avoid duplicating logic or bypassing the SDK entirely.
Scan code for defects that cause or are likely to cause incorrect behaviour at runtime. Do NOT flag style issues, naming conventions, or architectural preferences â only genuine bugs.
Translations cover 4 locales: **en, es, fr, ca**. These are the only supported locales â `STFUtils.supportedLanguages()` returns exactly this set. When in doubt, match existing code.
The goal is to keep every piece of AI-agent documentation accurate and up-to-date so that any agent can work confidently in any project without re-discovering facts that are already known.
This skill captures how Nx is **actually configured** in this repo. The workspace is an Angular-primary Nx monorepo managed with **yarn**. Always match existing patterns; never invent configuration that does not exist in this codebase.
Performance work in this codebase almost always comes down to these five areas: change detection discipline, signal memoisation, list rendering, lazy loading, and stream sharing. The patterns below encode what the team has adopted â follow them rather than inventing new approaches.
Two separate test stacks live in this repo. Match the stack to the project:
Auto-indexed from nuclia/frontend
Are you the author? Claim this skill to take ownership and manage it.
Related Skills
graceful-error-recovery
Use this skill when a tool call, command, or API request fails. Diagnose the root cause systematically before retrying or changing approach. Do not retry the same failing call without first understanding why it failed.
audience-aware-communication
Use this skill when writing any explanation, documentation, or response that will be read by someone else. Match vocabulary, depth, and format to the audience's expertise level before writing.
Refactoring Expert
Expert in systematic code refactoring, code smell detection, and structural optimization. Use PROACTIVELY when encountering duplicated code, long methods, complex conditionals, or any code quality issues. Detects code smells and applies proven refactoring techniques without changing external behavior.
Research Expert
Specialized research expert for parallel information gathering. Use for focused research tasks with clear objectives and structured output requirements.
clarify-ambiguous-requests
Use this skill when the user's request is ambiguous, under-specified, or could be interpreted in multiple ways. If proceeding with a wrong assumption would waste significant work, always ask exactly one focused clarifying question before doing anything.
structured-step-by-step-reasoning
Use this skill for any problem that involves multiple steps, tradeoffs, or non-trivial logic. Think out loud before answering to improve accuracy and transparency. Apply whenever the answer is not immediately obvious.