mariusflorescu/pstack-t3

sharpen

Make a task deeper, not bigger, then rewrite the prompt.

소스 보기

사용 방법

  1. 설치 명령을 복사하고 자신의 에이전트 환경에 설치하기 전에 소스 패키지를 확인하세요.
  2. 필요한 도구, 인증 정보, 지원 환경은 원본 문서에서 확인하세요.
  3. 입력과 원하는 산출물을 설명하고 출처와 결과를 대조하세요.
npx skills add https://github.com/mariusflorescu/pstack-t3 --skill sharpen

시작 전 확인

  • 설치에는 모델 구독, API 한도, 파일 접근 권한이 포함되지 않습니다.
  • 별점 수와 설치 수는 활동 지표이며 독립적인 품질·보안 검증이 아닙니다.
원본 Skill 문서

원본 저장소의 제목, 예시, 코드, 표, 링크, 이미지를 유지해 표시합니다.

I want a deeper version of this task, not a bigger one. Before rewriting it, do four things:

  1. Say what a top professional in this field would do here that I'm not asking for.
  2. Name the rawest material they would start from instead of what has already been digested for me.
  3. Name the specific methods and tools they would use.
  4. Say what, other than you or me, would show the result is right.

Then rewrite my prompt to ask for exactly that.

Leave choices that are mine to make open instead of deciding them.

관련 작업

같은 저장소의 Skills

더 많은 Skills

모든 Skills
mariusflorescu
커뮤니티

benchmark-checklist

Vet a perf measurement (limiter, tuning, limits, errors, repeatability, relevance, and whether the work happened) before you report or act on it. Use when you run a benchmark or report a speedup or regression you measured.

설치 수
1
GitHub Stars
13
업데이트
10월 20일
mariusflorescu
커뮤니티

blast-radius

Find what a change could break somewhere else before it ships, beyond the diff, and prove the one fact it's safe because of by running real code instead of writing it up. Use for 'blast radius of X', 'what could this break', or reviewing a small diff you don't trust.

설치 수
1
GitHub Stars
13
업데이트
10월 20일
mariusflorescu
커뮤니티

correct

Find the mistakes agents keep repeating in this repo and make each one impossible. Try architecture first, then types, then a lint whose error names the fix, then a test, and write docs last. Prove each check fails on a real past mistake. Repeat this each time the operator corrects you. Use for /correct.

설치 수
1
GitHub Stars
13
업데이트
10월 20일
mariusflorescu
커뮤니티

maintain-formal-verification-skill

Bring a project's formal verification back in line with the code after the code changes: find the commits that touched verified code, update the model, harness, or properties to describe the code as it is now, rerun, and say whether each failure is drift in the verification or a bug in the code. Use for /maintain-formal-verification-skill, \"is the model still true to the code\", or after merges and refactors that touched verified code without rechecking it.

설치 수
1
GitHub Stars
13
업데이트
10월 20일