ReddRadar
Topic: low-code
35 skills in this topic.
-
emil-design-eng
This skill encodes Emil Kowalski's philosophy on UI polish, component design, animation decisions, and the invisible details that make software feel great.
inkeep/agents 1,070
-
find-similar
Find similar or analogous code patterns elsewhere in a codebase.
Use when answering "Do we do something similar elsewhere?" or "What existing patterns match this?"
Returns factual findings about similar code - locations, similarity type, and confidence.
inkeep/agents 1,070
-
github-repo-sanity
Sanity-check GitHub repositories before citing, recommending, or comparing them.
Use when an agent refers to GitHub repos, OSS libraries, starter kits, templates, SDKs, MCP servers, or example projects.
Verify repo health using recent commit activity and adoption signals such as stars before recommending it.
Prefer active repos; explicitly flag stale, archived, or low-signal repos instead of presenting them as good defaults.
inkeep/agents 1,070
-
internal-surface-areas
Dependency graph of internal subsystems, infrastructure, and tooling (everything NOT customer-facing).
Use during planning, PR review, or refactoring to understand the internal ripple effects of a change.
Complements product-surface-areas (which covers customer-facing surfaces).
inkeep/agents 1,070
-
manage-database-usage
How to correctly access the Doltgres manage database with branch-scoped connections. Use when reading or writing manage data (agents, tools, projects, credentials, triggers, evaluators, etc.). Triggers on: manage database, withRef, c.get('db'), manageDbPool, branch checkout, doltgres, ref-scope, branchScopedDb, AgentsManageDatabaseClient.
inkeep/agents 1,070
-
next-best-practices
Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling
inkeep/agents 1,070
-
backend-code-review
Review backend code for quality, security, maintainability, and best practices based on established checklist rules. Use when the user requests a review, analysis, or improvement of backend files (e.g., `.py`) under the `api/` directory. Do NOT use for frontend files (e.g., `.tsx`, `.ts`, `.js`). Supports pending-change review, code snippets review, and file-focused review.
langgenius/dify 134,926
-
frontend-testing
Generate Vitest + React Testing Library tests for Dify frontend components, hooks, and utilities. Triggers on testing, spec files, coverage, Vitest, RTL, unit tests, integration tests, or write/review test requests.
langgenius/dify 134,926
-
frontend-query-mutation
Guide for implementing Dify frontend query and mutation patterns with TanStack Query and oRPC. Trigger when creating or updating contracts in web/contract, wiring router composition, consuming consoleQuery or marketplaceQuery in components or services, deciding whether to call queryOptions() directly or extract a helper or use-* hook, handling conditional queries, cache invalidation, mutation error handling, or migrating legacy service calls to contract-first query and mutation helpers.
langgenius/dify 134,926
-
frontend-code-review
Trigger when the user requests a review of frontend files (e.g., `.tsx`, `.ts`, `.js`). Support both pending-change reviews and focused file reviews while applying the checklist rules.
langgenius/dify 134,926
-
component-refactoring
Refactor high-complexity React components in Dify frontend. Use when `pnpm analyze-component --json` shows complexity > 50 or lineCount > 300, when the user asks for code splitting, hook extraction, or complexity reduction, or when `pnpm analyze-component` warns to refactor before testing; avoid for simple/well-structured components, third-party wrappers, or when the user explicitly wants testing without refactoring.
langgenius/dify 134,926