backend-dev

Coding practices for backend development in Atomic CRM. Use when deciding whether backend logic is needed, or when creating/modifying database migrations, views, triggers, RLS policies, edge functions, or custom dataProvider methods that call Supabase APIs.

Quality

82%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

64%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a well-structured, concise architectural decision guide that efficiently communicates when and how to use different backend patterns in Atomic CRM. Its main weaknesses are the lack of executable code examples (especially for the edge function middleware chain and custom dataProvider methods) and missing validation steps for database migrations and RLS policy changes.

Suggestions

Add a short executable code example showing the edge function middleware chain pattern (CORS → authenticate → handler) so Claude can copy-paste the structure.

Add a validation step for migrations: e.g., 'After creating a migration, test RLS policies with `supabase db reset` and verify the view returns expected columns.'

Include a brief code snippet showing how a custom dataProvider method calls an edge function via httpClient, making the integration pattern copy-paste ready.

Dimension	Reasoning	Score
Conciseness	Every sentence carries new, non-obvious information specific to this project's architecture. No explanation of what Supabase or PostgREST is—assumes Claude knows. The content is lean and dense with project-specific decisions.	3 / 3
Actionability	Provides concrete patterns (e.g., httpClient URL format, specific function names, middleware chain order, migration reference) but lacks executable code examples. The edge function convention description and dataProvider integration would benefit from a short code snippet showing the actual pattern.	2 / 3
Workflow Clarity	The decision tree (frontend-only vs view vs edge function) is clear, and the middleware chain is sequenced. However, there are no validation checkpoints for migrations (e.g., testing RLS policies, verifying views after column changes), and the migration workflow is implicit rather than explicit.	2 / 3
Progressive Disclosure	References migration `20260108160722` and shared utils path `supabase/functions/_shared/` but no bundle files are provided to support these references. The content is well-organized with clear sections but could benefit from explicit links to example files or a reference document for the shared utilities.	2 / 3
	Total	9 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a strong skill description that clearly defines its scope (backend development for Atomic CRM), lists specific concrete actions (migrations, views, triggers, RLS policies, edge functions, dataProvider methods), and includes an explicit 'Use when' clause with natural trigger terms. It uses proper third-person voice and is concise without being vague.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: database migrations, views, triggers, RLS policies, edge functions, and custom dataProvider methods that call Supabase APIs. These are all concrete, well-defined backend development tasks.	3 / 3
Completeness	Clearly answers both what ('Coding practices for backend development in Atomic CRM') and when ('Use when deciding whether backend logic is needed, or when creating/modifying database migrations, views, triggers, RLS policies, edge functions, or custom dataProvider methods that call Supabase APIs').	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'backend', 'database migrations', 'views', 'triggers', 'RLS policies', 'edge functions', 'dataProvider', 'Supabase'. These are terms developers naturally use when working on these tasks.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive with a clear niche: backend development specifically for Atomic CRM using Supabase. The combination of project name, technology stack, and specific backend artifacts (RLS policies, edge functions, dataProvider methods) makes it very unlikely to conflict with other skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: marmelab/atomic-crm
Commit: f46f3ab

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.