johnlindquist / johnlindquist/script-kit-next
Currently, the project feels a bit too bloated out of the box.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 28
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Things like notes, cleanshot, window-management, and other built-in features make the default structure more complex than necessary. It would be great if, after installation, users were presented with a relatively simple and clean setup.
Similar to v1, ideally users would only need to know about the scripts folder at the beginning, without needing to understand the rest of the internal structure.
As for these additional features, perhaps the official project could provide them as a set of optional plugins that users can choose to install, rather than bundling everything into the software by default.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by mapping the current default structure and the scripts folder entry point. Identify how notes, cleanshot, window-management, and other built-in features are included, then define a minimal post-install structure where these features can be added as optional plugins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100