RuleStack

Configs

Stacks

Compare

Diff

RuleStack

Configs

Stacks

Compare

Diff

Read API

RuleStack

Configs

Stacks

Compare

Diff

Read API

Configs/.cursorrules/Qwertic/cursorrules

.cursorrules (deprecated)

rules/graphical-apps-development-cursorrules-prompt-file/.cursorrules
.cursorrules

Quality

46/100

Scores the file, not the repository.

Length

452 words

1 headings · 0 code blocks

Repository

26

— · pushed 679 days ago

Last changed

3 days ago

First indexed 3 days ago.
Qwertic/cursorrules/rules/graphical-apps-development-cursorrules-prompt-file/.cursorrulesRawGitHub
1# Project SynopsisPyllments is a Python library for building graphical and API-based LLM applications through chaining together Elements in a potentially cyclic graph. Elements and Payloads are a type of Components. A Component is composed of a Model and Views. The Model handles the underlying data and logic, while the Views are the UI components that are used to display display the interactive UI used to interact with the Model. An Element is a type of Component that is responsible for a specific function. For instance, an Element can handle the LLM selection and generation by making calls to LLM providers. Another Element may handle the chat interface, whose Model would store the chat message history, and the Views would be the text boxes and buttons used to interact with the chat interface. Elements are meant to connect to other Elements through Ports. All that is necessary to link Elements together is to link the output port of one Element to the input port of Another. Each output port may have unlimited input ports it connects to, and each input port may have unlimited output ports it connects to. The ports follow an observer pattern where the output port is the subject and the input port is the observer. The subject notifies the observers when a certain event that we set within the Element is triggered. In order to connect an input and and output port, they need to be setup in a manner that sends and receives the same type of Payload. A Payload is also a Component with a Model as well as views responsible for the display logic. Elements may receive payloads and use methods of the Payload to generate the views for the UI. The sending Element is responsible for packing data into the Payload.  I am currently working on making this a fully-fledged framework.# Project OrganizationHere is an example of the file structure of an individual element:chat_interface:  - __init__.py  - chat_interface_element.py  - chat_interface_model.py  - css:    - buttons.css    - column.css    - input.css# Primary Libraries Used- Panel is used to create the visualization layer and run the GUI. Views tend to consist of Panel objects which can be styled with Python and CSS.- Param is used to create parameterized classes which help create parameters that handle type validation, default values, constraints, and most importantly, reactivity(setting event handlers to catch changes).- Langchain is responsible for the specific functions pertaining to incorporating LLM workflows.# Development PrioritiesPyllments code is prioritized on being developer-friendly, where extensibility and modularity are first-class citizens. Elements should be customizeable with clean and intuitive interfaces. It should also be easy to create new elements depending on the needs of the developer. # DocumentationDocstrings should use a NumPy/SciPy style.

Sections

  • Project SynopsisPyllments is a Python library for building graphical and API-based LLM applications through chaining together Elements in a potentially cyclic graph. Elements and Payloads are a type of Components. A Component is composed of a Model and Views. The Model handles the underlying data and logic, while the Views are the UI components that are used to display display the interactive UI used to interact with the Model. An Element is a type of Component that is responsible for a specific function. For instance, an Element can handle the LLM selection and generation by making calls to LLM providers. Another Element may handle the chat interface, whose Model would store the chat message history, and the Views would be the text boxes and buttons used to interact with the chat interface. Elements are meant to connect to other Elements through Ports. All that is necessary to link Elements together is to link the output port of one Element to the input port of Another. Each output port may have unlimited input ports it connects to, and each input port may have unlimited output ports it connects to. The ports follow an observer pattern where the output port is the subject and the input port is the observer. The subject notifies the observers when a certain event that we set within the Element is triggered. In order to connect an input and and output port, they need to be setup in a manner that sends and receives the same type of Payload. A Payload is also a Component with a Model as well as views responsible for the display logic. Elements may receive payloads and use methods of the Payload to generate the views for the UI. The sending Element is responsible for packing data into the Payload.  I am currently working on making this a fully-fledged framework.# Project OrganizationHere is an example of the file structure of an individual element:chat_interface:  - __init__.py  - chat_interface_element.py  - chat_interface_model.py  - css:    - buttons.css    - column.css    - input.css# Primary Libraries Used- Panel is used to create the visualization layer and run the GUI. Views tend to consist of Panel objects which can be styled with Python and CSS.- Param is used to create parameterized classes which help create parameters that handle type validation, default values, constraints, and most importantly, reactivity(setting event handlers to catch changes).- Langchain is responsible for the specific functions pertaining to incorporating LLM workflows.# Development PrioritiesPyllments code is prioritized on being developer-friendly, where extensibility and modularity are first-class citizens. Elements should be customizeable with clean and intuitive interfaces. It should also be easy to create new elements depending on the needs of the developer. # DocumentationDocstrings should use a NumPy/SciPy style.

What it covers

setupbuildcode-stylearchitecturetypesdependenciesapiui

Format

.cursorrules

Cursor's original single-file format, superseded by .cursor/rules/*.mdc. Tracked here precisely because it is dead: how much of the ecosystem is still shipping a deprecated file is a measurable answer, and a large share of the "best cursor rules" pages on the web still teach this format.

What the corpus says about it

Repository

Owner
Qwertic
Language
—
License
—
Archived
no

All configs in this repo

Also in Qwertic/cursorrules

Diff this repo’s formats

One repository carrying more than one format is the comparison this product exists for: does anyone actually write different content in each file, or is one a copy of the other?

The other instruction files in this repository
RepositoryFormatStackCoversScoreChanged
Qwertic/cursorrulesrules/next-type-llm/.cursorrules · 26.cursorrulesunclassifiedsecurity30/1003 days ago
Qwertic/cursorrulesrules/angular-typescript-cursorrules-prompt-file/.cursorrules · 26.cursorrulesunclassifiedtestdocs34/1003 days ago
Qwertic/cursorrulesrules/ascii-simulation-game-cursorrules-prompt-file/.cursorrules · 26.cursorrulesunclassifiedno sections34/1003 days ago
Qwertic/cursorrulesrules/astro-typescript-cursorrules-prompt-file/.cursorrules · 26.cursorrulesunclassifiedgit30/1003 days ago
Qwertic/cursorrulesrules/chrome-extension-dev-js-typescript-cursorrules-pro/.cursorrules · 26.cursorrulesunclassifiedstyle38/1003 days ago
Qwertic/cursorrulesrules/code-guidelines-cursorrules-prompt-file/.cursorrules · 26.cursorrulesunclassifiedstyletesting-strategydo-notagent-behaviour41/1003 days ago
Qwertic/cursorrulesrules/cursor-ai-react-typescript-shadcn-ui-cursorrules-p/.cursorrules · 26.cursorrulesunclassifiedno sections16/1003 days ago
Qwertic/cursorrulesrules/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup/.cursorrules · 26.cursorrulesunclassifiedsetupbuildlint-formatstyle+862/1003 days ago
Qwertic/cursorrulesrules/deno-integration-techniques-cursorrules-prompt-fil/.cursorrules · 26.cursorrulesunclassifiedno sections16/1003 days ago
Qwertic/cursorrulesrules/dragonruby-best-practices-cursorrules-prompt-file/.cursorrules · 26.cursorrulesunclassifiedstyle34/1003 days ago
Qwertic/cursorrulesrules/elixir-engineer-guidelines-cursorrules-prompt-file/.cursorrules · 26.cursorrulesunclassifiedno sections16/1003 days ago
Qwertic/cursorrulesrules/github-code-quality-cursorrules-prompt-file/.cursorrules · 26.cursorrulesunclassifieddo-notagent-behaviour37/1003 days ago
Qwertic/cursorrulesrules/github-cursorrules-prompt-file-instructions/.cursorrules · 26.cursorrulesunclassifiedno sections26/1003 days ago
Qwertic/cursorrulesrules/go-backend-scalability-cursorrules-prompt-file/.cursorrules · 26.cursorrulesunclassifiedno sections40/1003 days ago
Qwertic/cursorrulesrules/go-servemux-rest-api-cursorrules-prompt-file/.cursorrules · 26.cursorrulesunclassifiedno sections30/1003 days ago
Qwertic/cursorrulesrules/html-tailwind-css-javascript-cursorrules-prompt-fi/.cursorrules · 26.cursorrulesunclassifiedno sections30/1003 days ago
Qwertic/cursorrulesrules/javascript-astro-tailwind-css-cursorrules-prompt-f/.cursorrules · 26.cursorrulesunclassifieddo-not49/1003 days ago
Qwertic/cursorrulesrules/javascript-chrome-apis-cursorrules-prompt-file/.cursorrules · 26.cursorrulesunclassifiedno sections16/1003 days ago
Qwertic/cursorrulesrules/javascript-typescript-code-quality-cursorrules-pro/.cursorrules · 26.cursorrulesunclassifiedteststyletypesperformance+349/1003 days ago
Qwertic/cursorrulesrules/kubernetes-mkdocs-documentation-cursorrules-prompt/.cursorrules · 26.cursorrulesunclassifiedno sections16/1003 days ago
Diff against rules/next-type-llm/.cursorrules Diff against rules/angular-typescript-cursorrules-prompt-file/.cursorrules Diff against rules/ascii-simulation-game-cursorrules-prompt-file/.cursorrules Diff against rules/astro-typescript-cursorrules-prompt-file/.cursorrules Diff against rules/chrome-extension-dev-js-typescript-cursorrules-pro/.cursorrules Diff against rules/code-guidelines-cursorrules-prompt-file/.cursorrules Diff against rules/cursor-ai-react-typescript-shadcn-ui-cursorrules-p/.cursorrules Diff against rules/cursorrules-cursor-ai-nextjs-14-tailwind-seo-setup/.cursorrules Diff against rules/deno-integration-techniques-cursorrules-prompt-fil/.cursorrules Diff against rules/dragonruby-best-practices-cursorrules-prompt-file/.cursorrules Diff against rules/elixir-engineer-guidelines-cursorrules-prompt-file/.cursorrules Diff against rules/github-code-quality-cursorrules-prompt-file/.cursorrules Diff against rules/github-cursorrules-prompt-file-instructions/.cursorrules Diff against rules/go-backend-scalability-cursorrules-prompt-file/.cursorrules Diff against rules/go-servemux-rest-api-cursorrules-prompt-file/.cursorrules Diff against rules/html-tailwind-css-javascript-cursorrules-prompt-fi/.cursorrules Diff against rules/javascript-astro-tailwind-css-cursorrules-prompt-f/.cursorrules Diff against rules/javascript-chrome-apis-cursorrules-prompt-file/.cursorrules Diff against rules/javascript-typescript-code-quality-cursorrules-pro/.cursorrules Diff against rules/kubernetes-mkdocs-documentation-cursorrules-prompt/.cursorrules
RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack

RuleStack

Built by

Kynth Studio

Directory

Configs
Stacks
Compare formats
Diff two configs
Best AGENTS.md examples

Formats

AGENTS.md
CLAUDE.md
Cursor rules
Copilot instructions

Reference

Read API
Corpus health
Privacy Policy
Terms

RuleStack