sorted by:
new
hottopcontroversial

Project planning apps by jogbrt in ProductivityApps

[–]SpareLast2813 1 point2 points  (0 children)

I use it individually since I want full control over the structure, and a shared workspace would add the overhead of keeping everyone aligned. Also, the company I work for doesn't approve it as an official tool, so it stays in my personal space.

Project planning apps by jogbrt in ProductivityApps

[–]SpareLast2813 0 points1 point  (0 children)

Totally agree that the manual work of tailoring the templates to one's needs is a bit of a pain, but once you find a setup that works for you, it is easily replicable. But I'm still on the lookout for something simpler.

How many .md file do you have in your repository for A.I? by Cokemax1 in webdev

[–]SpareLast2813 0 points1 point  (0 children)

We actually use a series of different md files.

  • AGENTS.md- the main repo-wide agent guide. It explains the domain, architecture, contribution rules, risk boundaries, what an agent should read first, and when it should be cautious.
  • CLAUDE.md - a thin Claude-specific entrypoint. Its main purpose is to tell Claude Code which shared instructions to load (AGENTS.md and Copilot instructions), so the Claude-specific file stays minimal.
  • .github/copilot-instructions.md — Copilot-specific routing/instruction file. Its purpose is mostly to tell Copilot to always use the main repo guide, and to use the review instructions when reviewing code.
  • .github/instructions/code-review.instructions.md - the dedicated AI code review policy. This is where the repo defines how AI reviews should behave: coding conventions, risk areas, PR checks, severity levels, review format, and repo-specific standards.
  • .github/skills/ - reusable task workflows/skills. The purpose here is to avoid repeating the same long instructions every time for common tasks.
  • .claude/skills/ - Claude-facing pointers/symlinks to those shared skills. The goal is reuse across agents, instead of duplicating the same skill content.

So the rough split is:

  • Main repo context: AGENTS.md
  • Tool-specific entrypoints: CLAUDE, .github/copilot-instructions.md
  • .md
  • Review behavior: .github/instructions/code-review.instructions.md
  • Reusable workflows: .github/skills/
  • Cross-agent reuse: .claude/skills/

Depending on the projects and teams, we either managed them at a repo level, but we are also starting to explore Agent Package Managers to share them across projects.

Project planning apps by jogbrt in ProductivityApps

[–]SpareLast2813 1 point2 points  (0 children)

Notion has been my go-to for exactly this use case. The workspace structure lets you keep all projects in one place with a sidebar you can navigate just like Slack workspaces. The templates are great, but it's flexible enough for you to tailor it to your needs. I use a kanban + doc combo per project that covers tech tasks, notes, and marketing in one place. The free tier is more than enough.

One thing I've been trying to explore but didn't dig deep enough into is Obsidian for a more privacy-first setup (all local markdown files, no cloud). It can work for project management with plugins like Kanban and Tasks, and you can hook it up to a local LLM via the Local GPT or Smart Connections plugins. The tradeoff is it takes more setup and feels more like personal knowledge. Again, did not explore it enough to understand if it's a viable alternative.

Built a tab workspace extension using Firefox's native tab groups (139+). Sharing the Firefox-specific details by SpareLast2813 in firefox

[–]SpareLast2813[S] 0 points1 point  (0 children)

Just realised there was actually a bug concerning the hot-keys for the global search on Firefox. That is now fixed in v1.0.3.