apologies, the names is a little tongue in cheek. the goals of this is:

1. create an abstract syntax tree over the tree sitter trees for queries that work across language (function) @f matches functions in any supported language

2. create a smaller (in text) query language based on the semantics of css selectors e.g. in the 'c' language id#Validate -> [((function_definition declarator: (function_declarator declarator: (identifier) @_n0)) @_root2 (#eq? @_n0 "Validate")) ((call_expression function: (identifier) @_n1) @_root3 (#eq? @_n1 "Validate"))]

3. provide some useful commands on top of this to allow humans (and llms) to be able to quickly learn about codebases from the cli

i made this for myself, just sharing it because i probably should

yes i used claude code for most of this

Code review should be a separate function

Nah, theres not a technical or business solution to this. Music is cultural and we'll develop new cultural technology to solve it. Vision + regulation would help things move a little faster but the pendulums swing is inevitable.

We have to let go of old artists stuck in these patterns and find new, ideally local artists.

Yes

A local search indexer that indexes every page I visit (with tools for obvious exceptions) and lets me full text search them.

Is this some sort of paid for PR to divide the category of social media in the face of governments gearing up to regulate social media apps?

html encodes a tree of objects

css applies attributes to objects via graph queries

the queries are tightly coupled to the tree. you must work hard to avoid scatter gun edits now. it doesn't make much sense to have attributes stores in a separate location to their use

it would be like assigning all of your instances attributes using decorators

I suppose its a bit like winning a first person shooter game with aim assist on

It is not an authentic display of pure skill

the law of shitty click-throughs strikes again