Skip to content
Back to skills

Qstack Foundational Thinking

ASecurity

Settle data shape, access, ownership, concurrency, and useful shared setup before writing feature logic.

  • 7 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 5, 2026
ai-agentsgit

Works with

  • cursor

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned September 5, 2026

npx -y skills add hani-q/qstack --skill qstack-foundational-thinking --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Qstack Foundational Thinking?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Qstack Foundational Thinking
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/hani-q-qstack-foundational-thinking/badge)](https://www.skillsdirectory.com/skills/hani-q-qstack-foundational-thinking)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: qstack-foundational-thinking
description: Settle data shape, access, ownership, concurrency, and useful shared setup before writing feature logic.
disable-model-invocation: true
license: MIT
---

# Foundational thinking

Make the early structural choices that keep later work simple without deciding
more than the current requirements justify.

## Sequence the foundation

1. Subtract obsolete paths, redundant checks, and unused placeholders first.
2. Define the core data shape and invariants. Trace every important access path
   and choose structures that fit the dominant reads and writes.
3. Assign ownership. Before sharing mutable state, ask what happens when another
   actor changes it concurrently. Isolate it unless the answer is "nothing."
4. Add setup first only when every later phase benefits from it. CI, linting,
   test infrastructure, and shared types can be foundations; speculative
   frameworks are not.
5. Sequence tests before fixes and reusable setup before the features that need
   it. When commits are authorized, keep each one coherent and single-purpose.
6. Keep code-level decisions simple. Converge types and data models, but allow a
   few explicit repeated statements when an abstraction would add indirection.
7. Make each increment land or deepen one coherent domain boundary instead of
   spreading special-case coordination through callers.

Report the proposed data shape, access paths, ownership, concurrency boundary,
useful setup, and decisions intentionally deferred. Invocation authorizes only
the design or implementation scope the user requested, and never authorizes a
commit, push, publication, deployment, or external message by itself.

Adapted from Lauren Tan's PStack
[`principle-foundational-thinking`](https://github.com/cursor/plugins/blob/60c641e4fad674784b30abcf9f8915dea39df38d/pstack/skills/principle-foundational-thinking/SKILL.md)
at commit `60c641e4fad674784b30abcf9f8915dea39df38d` under the MIT License.
See [third-party notices](../../THIRD_PARTY_NOTICES.md).

Files in this skill

  • SKILL.md2 KB
  • agents/openai.yaml323 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.