agentleFS
atuinshatuinsh/desktop/.cursor/rules/component-creation.mdc

desktop / rules

Cursor rule2.5k starsChanged 19 months agoApache-2.0Archived repositoryView on GitHub

Writing a new block component for atuin runbooks

The file

We split this component-creation.mdc into the rules it gives an agent

12 rules. About 0 are common, 8 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Executable Blocks: - Run commands or execute actions (e.g., Run, Script, HTTP)

    line 29
  2. Very specific:

    Use createReactBlockSpec to define the block

    line 43
  3. Distinctive:

    Create Backend Command: if the component needs to interact with the system:

    line 48
  4. Very specific:

    Add module to backend/src/commands/mod.rs

    line 50
  5. Distinctive:

    When creating variable blocks (like Env or template Var):

    line 90
  6. Distinctive:

    Create a React component with input fields for name and value

    line 92
  7. Distinctive:

    Use props to manage state and sync with editor

    line 93
  8. Very specific:

    Use the component's onUpdate method to trigger backend state changes

    line 145
  9. Distinctive:

    Follow existing patterns for similar block types

    line 150
  10. Distinctive:

    Add tooltips to explain functionality

    line 152
  11. Very specific:

    Use @heroui/react components and lucide-react icons

    line 155
  12. Distinctive:

    When updating backend state, check that required values are present

    line 156

≈ “Common” is an estimate: at least 1 in 5 of the 6,668 Cursor rule files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
component-creation.mdc
---
description: Writing a new block component for atuin runbooks
globs: *.tsx, *.ts, *.rs
---
# Creating Components for Atuin Runbooks

Guidelines for creating new component blocks for the Atuin runbook editor.

<rule>
name: atuin_component_creation
description: Standards for creating and implementing component blocks in Atuin Desktop

filters:
  - type: event
    pattern: "file_create"
  - type: file_path
    pattern: "src/components/runbooks/editor/blocks/.*"

actions:
  - type: suggest
    message: |
      # Creating Components for Atuin Desktop
      
      ## Component Types
      
      There are two primary types of components:
      
      1. **Passive Blocks** - Provide context or configuration for other blocks (e.g., Directory, Env, Var, Host)
      2. **Executable Blocks** - Run commands or execute actions (e.g., Run, Script, HTTP)
      
      ## Component Structure
      
      ```
      src/components/runbooks/editor/blocks/[ComponentName]/
      ├── ComponentName.tsx  (or index.tsx)
      └── index.ts           (exports the component)
      ```
      
      ## Implementation Steps
      
      1. **Create Component Directory**
      2. **Create Main Component File**:
         - Use `createReactBlockSpec` to define the block
         - Implement a React component for the UI
      3. **Create Index File** for exports
      4. **Register in Schema** (`create_editor.ts`)
      5. **Add to Menu Items** (`Editor.tsx`) in the appropriate group
      6. **Create Backend Command** if the component needs to interact with the system:
         - Create in `backend/src/commands/[category].rs`
         - Add module to `backend/src/commands/mod.rs` 
         - Register command in main.rs (`tauri::generate_handler!`)
      
      ## Component Specification Example
      
      ```typescript
      export default createReactBlockSpec(
        {
          type: "your-component-type", 
          propSchema: {
            property: { default: "default-value" },
          },
          content: "none",
        },
        {
          render: ({ block, editor }) => {
            return <YourComponent {...props} />;
          },
        }
      );
      ```
      
      ## Suggestion Menu Item Example
      
      ```typescript
      export const insertYourComponent = (schema: any) => (editor: typeof schema.BlockNoteEditor) => ({
        title: "Component Name",
        subtext: "Description of component",
        onItemClick: () => {
          insertOrUpdateBlock(editor, {
            type: "your-component-type",
          });
        },
        icon: <SomeIcon size={18} />,
        group: "Appropriate Group", // Network, Execute, Database, etc.
      });
      ```
      
      ## For Passive Variable Blocks
      
      When creating variable blocks (like Env or template Var):
      
      1. Create a React component with input fields for name and value
      2. Use props to manage state and sync with editor
      3. For template variables, invoke a Tauri command to update backend state:
      
      ```typescript
      // In your component's render function:
      const onUpdate = (name: string, value: string): void => {
        // Update block props locally
        editor.updateBlock(block, {
          props: { ...block.props, name, value },
        });
        
        // Update backend state via command
        if (name && currentRunbookId) {
          invoke("set_template_var", {
            runbook: currentRunbookId,
            name,
            value,
          }).catch(console.error);
        }
      };
      ```
      
      ## Backend Command Structure
      
      For components that need backend state:
      
      ```rust
      // In backend/src/commands/template.rs
      #[tauri::command]
      pub async fn set_template_var(
          state: tauri::State<'_, crate::state::AtuinState>,
          runbook: String,
          name: String,
          value: String,
      ) -> Result<(), String> {
          // Update state logic here
          state
              .runbook_output_variables
              .write()
              .await
              .entry(runbook)
              .or_insert(HashMap::new())
              .insert(name, value);
      
          Ok(())
      }
      ```
      
      ## Architecture Guidelines
      
      - Commands using the Tauri API should live in `@commands` directory
      - Runtime functionality (without Tauri dependencies) lives in `@runtime`
      - Use the component's `onUpdate` method to trigger backend state changes
      - For passive blocks, use `findFirstParentOfType` and `findAllParentsOfType` to discover block values
      
      ## Best Practices
      
      - Follow existing patterns for similar block types
      - Maintain consistent styling with other blocks
      - Add tooltips to explain functionality
      - Group components properly in the menu
      - For passive blocks, use `findFirstParentOfType` to find parent blocks
      - Use `@heroui/react` components and `lucide-react` icons
      - When updating backend state, check that required values are present

examples:
  - input: |
      Creating a new Host block component
    output: |
      // Host component (src/components/runbooks/editor/blocks/Host/HostSelect.tsx)
      
      import { Button, Tooltip } from "@heroui/react";
      import { HomeIcon } from "lucide-react";
      import { createReactBlockSpec } from "@blocknote/react";
      import { insertOrUpdateBlock } from "@blocknote/core";
      
      const HostSelect = ({ isEditable }) => (
        <div className="w-full">
          <Tooltip content="Specifies that commands run on the local machine">
            <div className="flex flex-row items-center w-full">
              <div className="mr-2"><HomeIcon size={18} /></div>
              <div className="flex-grow">
                <Button variant="flat" className="w-full justify-start">localhost</Button>
              </div>
            </div>
          </Tooltip>
        </div>
      );
      
      export default createReactBlockSpec(
        {
          type: "host-select",
          propSchema: { host: { default: "local" } },
          content: "none",
        },
        {
          render: ({ block, editor }) => <HostSelect isEditable={editor.isEditable} />
        }
      );
      
      export const insertHostSelect = (schema) => (editor) => ({
        title: "Host",
        subtext: "Specify that commands run on localhost",
        onItemClick: () => { insertOrUpdateBlock(editor, { type: "host-select" }); },
        icon: <HomeIcon size={18} />,
        group: "Network",
      });
  
  - input: |
      Creating a template variable block that updates backend state
    output: |
      // Component definition (src/components/runbooks/editor/blocks/Var/index.tsx)
      import React from "react";
      import { Input, Tooltip, Button } from "@heroui/react";
      import { TextCursorInputIcon } from "lucide-react";
      import { invoke } from "@tauri-apps/api/core";
      import { useStore } from "@/state/store";
      import { createReactBlockSpec } from "@blocknote/react";
      
      const Var = ({ name, value, onUpdate, isEditable }) => {
        const handleKeyChange = (e) => {
          onUpdate(e.currentTarget.value, value);
        };
      
        const handleValueChange = (e) => {
          onUpdate(name, e.currentTarget.value);
        };
      
        return (
          <Tooltip content="Set a template variable for subsequent blocks">
            <div className="flex flex-row items-center space-x-2 w-full">
              <div className="flex flex-1 flex-row gap-2">
                <Button isIconOnly isDisabled variant="light">
                  <TextCursorInputIcon />
                </Button>
                <Input
                  placeholder="Name"
                  value={name}
                  onChange={handleKeyChange}
                  disabled={!isEditable}
                />
              </div>
              <div className="flex-1">
                <Input
                  placeholder="Value"
                  value={value}
                  onChange={handleValueChange}
                  disabled={!isEditable}
                />
              </div>
            </div>
          </Tooltip>
        );
      };
      
      export default createReactBlockSpec(
        {
          type: "var",
          propSchema: {
            name: { default: "" },
            value: { default: "" },
          },
          content: "none",
        },
        {
          render: ({ block, editor }) => {
            const currentRunbookId = useStore((store) => store.currentRunbookId);
            
            const onUpdate = (name, value) => {
              editor.updateBlock(block, {
                props: { ...block.props, name, value },
              });
              
              if (name && currentRunbookId) {
                invoke("set_template_var", {
                  runbook: currentRunbookId,
                  name,
                  value,
                }).catch(console.error);
              }
            };
      
            return (
              <Var
                name={block.props.name}
                value={block.props.value}
                onUpdate={onUpdate}
                isEditable={editor.isEditable}
              />
            );
          },
        },
      );
      
      // Backend command (backend/src/commands/template.rs)
      #[tauri::command]
      pub async fn set_template_var(
          state: tauri::State<'_, crate::state::AtuinState>,
          runbook: String,
          name: String,
          value: String,
      ) -> Result<(), String> {
          state
              .runbook_output_variables
              .write()
              .await
              .entry(runbook)
              .or_insert(HashMap::new())
              .insert(name, value);
      
          Ok(())
      }

metadata:
  priority: medium
  version: 1.1
</rule>

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.