「low-code」の検索結果

Appsmith is an open-source low-code platform for building internal tools, admin panels, and dashboards. Use when a user asks to create CRUD interfaces, connect to databases or APIs with drag-and-drop widgets, write JSObjects for business logic, or self-host Appsmith with Docker or Kubernetes.

日本語の概要は準備中です。原文の説明を表示しています。

Budibase is an open-source low-code platform for internal apps, forms, portals, and approvals. It gives agents a practical way to stand up operational tools on top of PostgreSQL, REST APIs, and other business data sources with self-hosted deployment options.

日本語の概要は準備中です。原文の説明を表示しています。

Build no-code/low-code automation workflows for construction using n8n. Automate data extraction, cost estimation, report generation, and system integrations without writing code.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews React Flow code for anti-patterns, performance issues, and best practices. Use when reviewing code that uses @xyflow/react, checking for common mistakes, or optimizing node-based UI implementations.

日本語の概要は準備中です。原文の説明を表示しています。

Use when scoring a list of business or solution requirements against the *actual* capabilities of a specific Salesforce org so each row can be classified Standard / Configuration / Low-Code / Custom / Unfit, given an effort tier (S/M/L/XL), a risk tag, and an AppExchange suggestion when applicable. Trigger keywords: fit gap salesforce requirements, score requirements against salesforce capabilities, salesforce capability matrix, classify requirement as standard config custom, fit-gap effort tier, AppExchange alternative for requirement. NOT for requirements elicitation (use admin/requirements-gathering-for-sf). NOT for architecture decisions on the GAP rows (use architect/solution-design-patterns and standards/decision-trees/). NOT for license or edition selection (use architect/license-optimization-strategy and architect/org-edition-and-feature-licensing). NOT for OmniStudio-specific fit-gap (use architect/omnistudio-vs-standard-decision).

日本語の概要は準備中です。原文の説明を表示しています。

[Workflow] Use when activating the Idea-to-Spec workflow — turn a raw idea/vision/problem into ONE canonical (provisional) Feature Spec. STOPS at the reviewed spec; chain workflow-spec-to-pbi for a backlog. For code→spec use workflow-code-to-spec.

日本語の概要は準備中です。原文の説明を表示しています。

[Workflow] Use when activating code-to-spec development — author/maintain the single canonical Feature Spec FROM existing code, keeping spec, implementation, and tests synchronized. For idea→spec (no code yet) use workflow-idea-to-spec.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Budibase — budibase low-code platform management covering application inventory, table and datasource health, screen layout analysis, automation monitoring, and user role auditing. Use when reviewing internal app configurations, investigating data connectivity issues, monitoring automation runs, or auditing user access controls.

日本語の概要は準備中です。原文の説明を表示しています。

Use when working with Appsmith — appsmith low-code platform management covering application inventory, workspace organization, datasource health, page and widget analysis, and user access auditing. Use when reviewing internal tool configurations, investigating datasource connectivity, monitoring application deployments, or auditing workspace permissions.

日本語の概要は準備中です。原文の説明を表示しています。

Busabase-backed App-in-Skill low-code agent configuration and governance console for a platform team. Use when the user invokes $kelly-agent-builder or /kelly-agent-builder, wants to review or edit a catalog of mock LLM agent configs, check quota usage, find configs that need attention, move a draft to live, pause a live agent, or archive an agent. Mock config/governance console only — it never provisions or calls any real agent.

日本語の概要は準備中です。原文の説明を表示しています。